-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Nvm has fallen to AI slop:
fnm looks viable, but it appears to have at least one PR author that really enjoys AI slop, so it's too much of a risk (which is a shame, I enjoyed fnm before I had to wipe that machine due to completely unrelated technical difficulties):
- Dargon789 patch 2 Schniz/fnm#1479
- Renovate/actions setup node 4.x Schniz/fnm#1473
- fix: Update release-to-cargo.yml (#55) config to base:br master Schniz/fnm#1474
- ... etc, there's like 5 PRs and I don't feel like linking to them all
None of these have been approved nor allowed to run, but they also haven't been disallowed, so it's a coinflip on whether or not fnm falls to AI slop.
Some other commonly cited options:
- https://github.com/tj/n (clean, but the author has not been active on github in years. Someone else has taken over from what I can tell)
- https://github.com/volta-cli/volta (clean, but large-scale project; probability of falling is unacceptably high)
upm is one patch away from working (@24 needs to link to latest-v24 instead of v24), and I think that's my best choice. Might need to consider making it a proper version manager at some point, but that's a problem for future me. In theory, it should just be a matter of adding the stuff to the PATH and calling it a day. Will investigate Later:tm:. I do believe some programs will struggle with this though, node and python in particular being at a high risk due to arbitrary path bullshit