Closed ewapotorecka closed 1 year ago
As a workaround, you may use:
npx @teambit/bvm install --use-system-node
thank you,
this will also work with bvm upgrade
?
And are you planning on fully supporting m1 in the near future and if yes when?
Yes, it is supported by bvm upgrade
. You can see the list of supported options by running bvm upgrade -h
I think m1 should be support already. It must be some bug.
@giteden we have to document this issue
please make sure you are using latest version of bvm (0.2.10 at the moment)
(the npx is not always updating global bins)
(so better to just install bvm globally)
then run bvm upgrade --override
and it will install the correct version according to your architecture.
if the node that exist in the bvm folder is incorrect, you can delete the nodejs folder there before running the bvm upgrade.
and bvm will re-fetch it.
if it doesn't work, it usually means that your node version that is used to install bvm (the machine installed version of node) is not the arm64 version.
you can check it by just running node -p 'process.arch'
and make sure it prints arm64
if not, you need to uninstall node, and re-install a proper version of node.
Describe the bug
After installing (or updating to the newest version), when I try to run
bit tag
I get an error:Error: You installed esbuild on another platform than the one you're currently using. This won't work because esbuild is written with native code and needs to install a platform-specific binary executable.
For installing bit I've used the command from the documentation:
npx @teambit/bvm install
.I've checked and Node.js is being installed in
~/.bvm/nodejs
and it targetsx64
instead ofarm64
, which is causing the issue.Other
bit
commands also don't work correctly.Steps to Reproduce
Expected Behavior
After installing or updating
bit
, it uses the correct build of Node.js for m1 architecture.Specifications