-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Feature Request: Unofficial builds #3041
Comments
Note: I put "PR wanted" on this, but I'm still very unclear about whether this can be added cleanly. I'd love to see a suggested implementation. |
That would be also very useful for RISC-V machines, I see that files like node-v20.5.1-linux-riscv64.tar.xz are available for download, but Is there anything that can be done to speed up installs on RISC-V machines? |
FWIW, the override in #3251 (which we're applying to our local install of nvm as a patch) is working well for us on CentOS 7, allowing us to install unofficial builds, check for updates etc. Without being able to add the Obviously this (being stuck on CentOS 7) is not a situation we want to be in long term, but for now this solution is preventing major dependency update headaches. |
There is a very easy workaround if you know you want an unofficial build, by setting NVM_NODEJS_ORG_MIRROR to https://unofficial-builds.nodejs.org/download/release/. I assume that a propoer implementation would be to have musl instead of std for the function nvm_get_mirror. |
@ljharb We recently talked about how it makes no sense to have a POSIX compliant installer, since on embedded systems you most likely need to compile node yourself, so the benefit of not installing bash is neglectable.
The reason why nvm doesn't work on Alpine Linux, is because the official builds are compiled against glibc, but there are unofficial builds for musl that should work.
It would be beneficial to have a way to define a different source for node versions, so that I can use nvm on Alpine in the first place.
node releases on the Alpine package manager are tied to repository branches, meaning accessing an older node version means to run an ancient OS as well. I'd love if you could look into it.
Related: nodejs/build#1140
The text was updated successfully, but these errors were encountered: