Why do I get "Error: Cannot find module '@swc/core-linux-x64-gnu'" in Github actions?

[alexbjorlig]

I'm using Github actions, with their ubuntu-latest latest image. I'm using @swc/jest and works perfect on my local machine. But when I run Github actions I often get this error:

Run ./node_modules/.bin/jest --config jest.config.integration.cjs --maxWorkers 1 --forceExit --reporters=default --reporters=jest-junit
Error: Cannot find module '@swc/core-linux-x64-gnu'
Require stack:
- /home/runner/work/eddystone/eddystone/node_modules/@swc/core/binding.js
- /home/runner/work/eddystone/eddystone/node_modules/@swc/core/index.js
- /home/runner/work/eddystone/eddystone/node_modules/@swc/jest/index.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-util/build/requireOrImportModule.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-util/build/index.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-config/build/getCacheDirectory.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-config/build/Defaults.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-config/build/normalize.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-config/build/index.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-cli/build/init/index.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-cli/build/cli/index.js
- /home/runner/work/eddystone/eddystone/node_modules/jest-cli/bin/jest.js
- /home/runner/work/eddystone/eddystone/node_modules/jest/bin/jest.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/runner/work/eddystone/eddystone/node_modules/@swc/core/binding.js:181:[45](https://github.com/21RISK/eddystone/runs/5677485932?check_suite_focus=true#step:10:45))
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:11[55](https://github.com/21RISK/eddystone/runs/5677485932?check_suite_focus=true#step:10:55):10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
Error: Process completed with exit code 1.

What could this be?

My package.json looks like this:

        "@swc/core": "^1.2.160",
        "@swc/jest": "^0.2.20",

[kwonoj]

Are optional dependencies installed on the CI correctly?

[kwonoj]

Question was how do you install it in ci. Having a reproducible repo would be helpful to investigate, current log doesn't have any information why it fails.

[alexbjorlig]

Thanks - I found something about optional dependencies, and this fixed the issue:

"optionalDependencies": {
        "@swc/core-linux-x64-gnu": "^1.2.160"
    }

[kwonoj]

swc/core have it as optional dependency already, so if you have to manually specify it something is not correct.

[skitsanos]

@alexbjorlig adding optionals worked for me as well on CircleCI

[Mheaus]

Worked for me with github actions.

[skitsanos]

Having a similar issues:

> @********/[email protected] postinstall
> swc ./src --delete-dir-on-start -d dist

/home/circleci/project/node_modules/@swc/core/binding.js:242
        throw loadError;
        ^

Error: Cannot find module '@swc/core-linux-x64-gnu'

CircleCI fails, while locally it all works just fine and even can use dependency directly from github, for some reason not in CricleCI

[kwonoj]

npm ci cannot run without package-lock.json. is it npm ci or just npm install without lockfile?

[skitsanos]

true that. but for now i made it work with optionals

[asztal]

I've seen the same issue. It seems to be because I installed the package on my MacBook (which therefore chose to add @swc/core-darwin-x64 to package-lock.json) but then my CI is linux-based so it's trying to load @swc/core-linux-x64-gnu.

I guess this is because the package.json for @swc/core-linux-x64-gnu specifies { os: "linux", cpu: "x64" } so on my Mac npm decides that it can't be installed. It doesn't seem like there's an easy solution though, except removing the { os: "linux", cpu: "x64" } which would mean that everyone will by default download the 39MB linux-x64-gnu version even if they don't need it.

If I remember correctly, other projects (like node-sass) have approached this by having a postinstall script which downloads the correct binary, rather than having npm manage fetching the native code.

[kdy1]

The package lock does not matter.
npm will download linux version on ci even if your local machine is mac

You should not upload node_modules to git

[Brooooooklyn]

it seems to be because I installed the package on my MacBook (which therefore chose to add @swc/core-darwin-x64 to package-lock.json) but then my CI is linux-based so it's trying to load @swc/core-linux-x64-gnu.

It should be a bug of the npm client, optionalDependencies should always be present in the package-lock.json file, wherever the lock file was generated

[ivantm]

This issue on the npm cli seems relevant: npm/cli#4828

Deleting node_modules and package-lock.json usually helps regenerate a correct package-lock.json that will work in CI for me.

[datenreisender]

That issue was finally fixed in npm/cli#8184 and released in npm 11.3.0 🎉

[kwonoj]

this should go @rspack.