Skip to content

fix: lint in ssz package #2398

fix: lint in ssz package

fix: lint in ssz package #2398

Triggered via push February 12, 2025 12:18
Status Failure
Total duration 1m 49s
Artifacts

test.yml

on: push
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 2 warnings
Tests (18)
Cannot find module '@dapplion/benchmark' or its corresponding type declarations.
Tests (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../../src/util/merkleize.js'?
Tests (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../lodestarTypes/params.js'?
Tests (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (18)
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (18)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (18)
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (18)
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (18)
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (20)
Cannot find module '@dapplion/benchmark' or its corresponding type declarations.
Tests (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../../src/util/merkleize.js'?
Tests (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../../lodestarTypes/params.js'?
Tests (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (20)
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (20)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
Tests (20)
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (20)
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (20)
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha`.
Tests (18)
Cache not found for keys: node-cache-Linux-x64-yarn-b2a59f3de07b6945202f5d58624e7c8cc62c753484f0ecf38a0b090c449f81fd
Tests (20)
Cache not found for keys: node-cache-Linux-x64-yarn-b2a59f3de07b6945202f5d58624e7c8cc62c753484f0ecf38a0b090c449f81fd