Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

github.com

Post reply on HN
Print view View original

41–50 of 71 posts

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#41

Post by csixty4 »

josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

For us, it's about developing on the same node version used in production. That's necessary if you're not deploying to a containerized environment or you're using something completely out of your control like AWS Lambda.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#42

Post by giancarlostoro »

josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

Sometimes you're limited in production by whatever version the OS supports. In the case of Debian installing nodejs doesn't necessarily land you the latest and greatest. The same happens with Python as well. I wish they had a good way to abstract this in Debian and I'm surprised Ubuntu hasn't fully resolved it, I mean Ubuntu does have Snap but I can't trust Snaps fully if the language vendors aren't backing the only available Snaps. But to account for systems where the only version of Node or Python, or whatever is a specific version, you need systems like this.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#43

Post by bepvte »

josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

the main reason i use nvm is because its the only way i can use npm i -g.....

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#45

Post by josteink »

bepvte wrote: post #43
josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

the main reason i use nvm is because its the only way i can use npm i -g.....

You dont need to nvm to do that. You just need to set an alternate "global" path inside your home-directory, instead of one in /usr/lib/node which requires root.

https://stackoverflow.com/questions/14742553/how-to-set-cust...

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#46

Post by devmunchies »

badhombres wrote: post #39
josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

When I write lambda code for my job, our code currently only supports the node 6 for it's runtime (our system automatically deploys it). I use nvm to help test my code all the time while still having the ability to switch to a more current node for other projects

Are you running your projects directly on your machine? Your’re not using a VM or containers? Don’t you have the “but it works on my machine” problem?

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#47

Post by mvarrieur »

dual_basis wrote: post #44

Naming conflict with Fish Node Manager ( https://github.com/jorgebucaran/fish-nvm ), a wrapper of NVM for the fish shell.

Yup came here to say this, although I have recently had issue with the Fish Node Manager which had me revert to using nvm.

Issues which made it unusable completely every time I tried to use node it could no longer find the node/npm binaries.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#48

Post by jjuel »

giancarlostoro wrote: post #42
josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

Sometimes you're limited in production by whatever version the OS supports. In the case of Debian installing nodejs doesn't necessarily land you the latest and greatest. The same happens with Python as well. I wish they had a good way to abstract this in Debian and I'm surprised Ubuntu hasn't fully resolved it, I mean Ubuntu does have Snap but I can't trust Snaps fully if the language vendors aren't backing the only…

You can absolutely install the newest version of Python and Node on Debian. It is a little harder than just an `apt-get install`, but very possible.

Re: Show HN: Fnm – Fast and simple Node.js version manager built in ReasonML

#50

Post by Touche »

josteink wrote: post #37

Maybe I'm completely out of the loop, but what's the deal with running multiple versions of Node? What particular problems or projects do you have where this is a pressing necessity? I just install latest LTS and keep that up to date, and I've yet to find a single thing not working.

Here's a couple of use cases:

You maintain a library and you support more than just the latest version of Node. You switch to test compatibility.

You work on a project with a team. Some members of the team work on other projects with other versions of Node. They need to be able to switch.

Post reply on HN