Fix ReferenceError: Cannot access 'TwitterApiReadWrite' before initia… #493
Annotations
10 errors and 2 warnings
|
Run npm ci:
src/client/readonly.ts#L1
Argument of type '{ appKey: string; appSecret: string; accessToken: string; accessSecret: string; }' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/client/readonly.ts#L1
Argument of type '{ username: string; password: string; }' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/client/readonly.ts#L1
Argument of type 'string' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/client/readonly.ts#L1
Argument of type 'string' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/test/utils.ts#L1
Argument of type '{ appKey: string; appSecret: string; accessToken: string; accessSecret: string; }' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/test/utils.ts#L1
Argument of type '{ appKey: string; appSecret: string; }' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/test/utils.ts#L1
Property 'generateAuthLink' does not exist on type 'TwitterApi'.
|
|
Run npm ci:
src/test/utils.ts#L1
Argument of type '{ appKey: string; appSecret: string; accessToken: string; accessSecret: string; }' is not assignable to parameter of type 'TwitterApiBase'.
|
|
Run npm ci:
src/test/utils.ts#L1
Property 'login' does not exist on type 'TwitterApi'.
|
|
Run npm ci:
src/test/utils.ts#L1
Argument of type 'string' is not assignable to parameter of type 'TwitterApiBase'.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading