You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try to install an older version of node without a precompiled arm binary, nvm will automatically download the x86-64 version instead. asdf-nodejs will instead try (and almost certainly fail) to compile the version from the source and to get a precompiled version the user has to manually specify the architecture by running $ arch -x86_64 asdf install nodejs <version> instead which is much less user friendly.
The text was updated successfully, but these errors were encountered:
asdf-nodejs currently already tries to build the said version from source as a fallback. I'm not sure which behavior would be the most useful for mac users. It seems like most people are content with either building it or running arch -x86_64 for installing the x64 version
If this gets enough traction, we can try to think something about it, maybe an environment variable to control it
It would be better to install x86_64 by default, because there are lot of precompiled npm dependencies in x86_64 that can not be invoked by nodejs in ARM.
It would be a lot worse if we sometimes installed x86 ones and sometimes ARM ones without explicitly passing that as an option.
This could effectively be opting into a race condition where if the x86 binary gets published before the arm one, some users would be on x86 instead of ARM.
If you try to install an older version of node without a precompiled arm binary, nvm will automatically download the x86-64 version instead. asdf-nodejs will instead try (and almost certainly fail) to compile the version from the source and to get a precompiled version the user has to manually specify the architecture by running
$ arch -x86_64 asdf install nodejs <version>
instead which is much less user friendly.The text was updated successfully, but these errors were encountered: