-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 arm64 linux installs x64 linux binary #4717
Comments
I don't have a linux arm device to test this on at the moment, but do you get the same thing when you run |
This comment was marked as resolved.
This comment was marked as resolved.
cc @danlapid |
Any arm64 linux trying to run |
Does installing https://www.npmjs.com/package/@biomejs/cli-linux-arm64 manually fix your issue? If so, the package manager isn't installing the optional dependencies of your system. |
The standalone binary works as expected, yes
|
That's not exactly what I was asking sorry (or maybe I misunderstood the answer). Can you install If this works, it means the package manager is the issue, and maybe your architecture isn't recognised by the package managers. This is the matrix of the package: {
"os": [
"linux"
],
"cpu": [
"arm64"
],
"libc": [
"glibc"
]
} |
Not sure what I'm doing wrong here:
|
You need to install |
No luck:
|
It seems like we aren't aligned. I need you to run this: pnpm i @biomejs/biome
pnpm i @biomejs/cli-linux-arm64
pnpm exec biome --version |
Ok, here's the log: build@machine:~/directory$ pnpm i @biomejs/biome
Packages: +3
+++
Progress: resolved 266, reused 238, downloaded 0, added 0, done
The following dependencies have build scripts that were ignored: @biomejs/biome
dependencies:
+ @biomejs/biome 1.9.4
WARN Issues with peer dependencies found
.
└─┬ eslint-plugin-import 2.30.0
└── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8": found 9.10.0
Done in 939ms
build@machine:~/directory$ pnpm i @biomejs/cli-linux-arm64
Already up to date
Progress: resolved 266, reused 238, downloaded 0, added 0, done
dependencies:
+ @biomejs/cli-linux-arm64 1.9.4
WARN Issues with peer dependencies found
.
└─┬ eslint-plugin-import 2.30.0
└── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8": found 9.10.0
Done in 830ms
build@machine:~/directory$ pnpm exec biome --version
node:internal/modules/cjs/loader:1251
throw err;
^
Error: Cannot find module '@biomejs/cli-linux-x64/biome'
Require stack:
- /home/build/directory/node_modules/.pnpm/@[email protected]/node_modules/@biomejs/biome/bin/biome
at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
at Function.resolve (node:internal/modules/helpers:135:19)
at Object.<anonymous> (/home/build/directory/node_modules/.pnpm/@[email protected]/node_modules/@biomejs/biome/bin/biome:51:11)
at Module._compile (node:internal/modules/cjs/loader:1546:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1691:10)
at Module.load (node:internal/modules/cjs/loader:1317:32)
at Module._load (node:internal/modules/cjs/loader:1127:12)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:166:5) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/home/build/directory/node_modules/.pnpm/@[email protected]/node_modules/@biomejs/biome/bin/biome'
]
}
Node.js v22.6.0 |
I'm not sure what's the issue here. You claim to have arm64 linux, so I would expect to see Here's what the Node.js script uses for retrieving the info:
@anonrig can you help here? |
Ok I think I may understand part of the puzzle, I ran:
So I seem to have x86_64 bit node on my arm64 vm (the vm is running on top of a mac with rosetta translation since I'm working on a project that only supports linux targets). |
https://stackoverflow.com/questions/7897678/get-processor-architecture-from-node seems to be relevant. |
One way of doing this is through
|
I don't have that variable defined:
|
Environment information
What happened?
pnpm i --save @biomejs/biome
Expected result
It should properly detect arm64
Code of Conduct
The text was updated successfully, but these errors were encountered: