-
Notifications
You must be signed in to change notification settings - Fork 210
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
Support specific node versions instead of just majors #1017
Comments
100% This is an issue we see at Railway too. You can use https://lazamar.co.uk/nix-versions/ to find a specific version of a package, but it is not ideal. We've been trying a few things internally, but nothing prioritized at the moment. Very open to ideas or suggestions though. |
Could we stop using nix for nodejs and instead use something like fnm ? |
Yes that is possible. Alternatively we could switch to something like asdf. It would be a pretty fundamental change to Nixpacks though. Which I am not against, but would just need to weigh the options and decide of moving away from Nix for managing packages is the best option for managing packages. |
In case it's helpful, I've been using I'd love to see it baked into nixpacks somehow though, maybe as an optional layer on top of the existing setup? |
Feature request
This is a recurring frustration for our users, they expect to be able to set a specific node version instead of only a major.
Currently the only workaround I know of is to go spelunking in nixpks repo and find the commit for a certain version and then pin that version in nixpacks.toml. But this process is almost impossible to explain to users.
The text was updated successfully, but these errors were encountered: