Skip to content
Triggered via pull request October 8, 2024 16:06
@RubilmaxRubilmax
synchronize #113
feat/vitest
Status Failure
Total duration 2m 6s
Artifacts

test.yml

on: pull_request
Matrix: packages
Fit to window
Zoom out
Zoom in

Annotations

26 errors
packages (blue-sdk, true, true) / hardhat
Process completed with exit code 1.
packages (blue-sdk-ethers-liquidation, false, true) / hardhat
Process completed with exit code 1.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-sdk-ethers, true, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
packages (blue-api-sdk, false, false) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
packages (blue-api-sdk, false, false) / build
Process completed with exit code 1.
packages (blue-sdk-ethers-liquidation, false, true) / build
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
Cannot find module '@morpho-org/blue-sdk-ethers-liquidation/src/contracts/curve' or its corresponding type declarations.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-api-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers-liquidation, false, true) / build
Cannot find module '@morpho-org/blue-sdk-ethers-liquidation/src/contracts/curve' or its corresponding type declarations.
packages (blue-sdk-ethers-liquidation, false, true) / build
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("@morpho-org/blue-sdk")' call instead.
packages (blue-sdk-ethers, true, true) / hardhat
Process completed with exit code 1.
packages (blue-sdk-viem, false, true) / hardhat
Process completed with exit code 1.