Add a script for create contract metadata migration #36
Annotations
7 errors and 2 warnings
|
Verify TypeScript compilation:
src/lazy-migrations/004-create-contract-metadata.ts#L14
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/networks.js'?
|
|
Verify TypeScript compilation:
src/lazy-migrations/004-create-contract-metadata.ts#L18
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/monitoring.js'?
|
|
Verify TypeScript compilation:
src/lazy-migrations/004-create-contract-metadata.ts#L19
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/constants.js'?
|
|
Verify TypeScript compilation:
src/lazy-migrations/004-create-contract-metadata.ts#L113
Argument of type 'unknown' is not assignable to parameter of type 'number'.
|
|
Verify TypeScript compilation:
src/lazy-migrations/get-contracts-without-metadata.ts#L7
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../utils/networks.js'?
|
|
Verify TypeScript compilation:
src/lazy-migrations/get-contracts-without-metadata.ts#L119
No overload matches this call.
|
|
Verify TypeScript compilation
Process completed with exit code 2.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. 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@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading