Closed thanhlmm closed 6 months ago
What is your setup? WSL?
I have the same issue locally on windows and all of my CI (Linux) experience the same issue. I've tried installing it normally with pnpm
, I've tried installing it globally with npm
, yarn
, and pnpm
. Nothing works.
It started yesterday on CI.
Example error (yarn on linux in this case):
Run yarn global add @subsquid/cli@latest
yarn global v1.22.21
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
error /home/runner/.config/yarn/global/node_modules/@subsquid/cli: Command failed.
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
Exit code: 1
Command: node ./bin/run.js autocomplete --refresh-cache
Arguments:
Directory: /home/runner/.config/yarn/global/node_modules/@subsquid/cli
Output:
› ModuleLoadError: [MODULE_NOT_FOUND] require failed to load
› /home/runner/.config/yarn/global/node_modules/@subsquid/cli/lib/commands:
› Cannot find module
› '/home/runner/.config/yarn/global/node_modules/@subsquid/cli/lib/commands'
› Require stack:
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/module-loa
› der.js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/help/index
› .js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/flags.js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/cli-ux/sty
› led/table.js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/cli-ux/sty
› led/index.js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/cli-ux/ind
› ex.js
› - /home/runner/.config/yarn/global/node_modules/@oclif/core/lib/index.js
› - /home/runner/.config/yarn/global/node_modules/@subsquid/cli/bin/run.js
› Code: MODULE_NOT_FOUND
MacOS. The root cause of @oclif/core
new version
The root cause of
@oclif/core
new version
If this is saying that @oclif/core
is the root cause: I'm not sure. I resolved it to 3.20.0
(last week) and the issue still persists.
The root cause of
@oclif/core
new versionIf this is saying that
@oclif/core
is the root cause: I'm not sure. I resolved it to3.20.0
(last week) and the issue still persists.
3.19.1 will work bro
Should be resolved in subsquid/cli@2.8.7
. We locked oclif version for now.
I can confirm the issue is resolved via subsquid/cli@2.8.7
. Thank you for the quick turnaround!
When I run
It returns error