Nodejs Version Managers
-
No intention to start a religious war here but I come from sysadmin/engineer rather than developer background and the nodejs version manager landscape seems pretty littered. I've been unable to find roundups or analysis that are not ancient and I am not motivated to make a study of it. A few pros and cons of the modern day favorites would be appreciated for the lazy.
Yes, I am aware that virtual images have supplanted much of the need for version managers but humor me.
TIA o/
P.S.; Feel free to move this to Dev if more appropriate. Not nodeBB specific so I opted for here.
-
In my experience there are few reasons to use a version manager, except for development reasons (i.e. testing on older versions of Node, etc.)
In production, I am increasingly in favour of compartmentalization via containers (or currently, simply separate servers). They can each maintain their own version of Node via the OS package manager, and that's that.
-
@julian said in Nodejs Version Managers:
In my experience there are few reasons to use a version manager, except for development reasons (i.e. testing on older versions of Node, etc.)
In production, I am increasingly in favour of compartmentalization via containers (or currently, simply separate servers). They can each maintain their own version of Node via the OS package manager, and that's that.
Yep. I concur one hundred percent with the separate vm's for production approach. I don't think I'd utilize containers directly unless I owned the bare metal and needed to leverage that investment for additional duties. And then I'd use a better hypervisor and launch a Linux vm from there.
I sometimes muck about with different nodejs based stuff that wants different versions, requirements, and such and thought it might be nice to forgo spinning up vm's for the quick exploratatories....
None of them seem to want to play nicely with FreeBSD these days though so the question seems rather moot for my use case.
Thanks for your thoughts.
