Skip to content

chore: update repo

chore: update repo #5

Triggered via push February 6, 2024 13:09
Status Failure
Total duration 30s
Artifacts

check.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 1 warning
check: tests/rest/carry-fees-history.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/carry-fees-history.spec.ts#L14
Parameter 'err' implicitly has an 'any' type.
check: tests/rest/fixing-history.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/index-history.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/options-instruments.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/options-market.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/price-history.spec.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check: tests/rest/ticker.spec.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../src/rest.js'?
check
Process completed with exit code 1.
check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pnpm/action-setup@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.