Sorry: that was sent in a hurry from a mobile so I didn't include a link.
Node Version Manager (nvm) is a really useful tool for installing and managing node installations. It makes installing node a trivial one line command. It also allows installation of multiple versions of node and to switch between these using a single command; or IIRC even using a project level config file.
It's especially useful if working on multiple projects which may have dependencies on different node versions. Or running a project against the version of node available on the deployment server (to ensure you're developing/testing against the correct version) whilst still being able to try out a bleeding edge release locally.
So you're not tied to using the one version you installed using the method you described ;)
Sounds amazing, in a way I guess it would be kinda like the concept of a container, I will look more into how to install NVM hopefully is not that complicated
IIRC it's fairly straightforward to install. I think the only possible problem that may crop up is ensuring the command is available on your PATH; but I'm pretty sure that's already documented.
The other thing to be careful of is what version you currently have active; since some dependencies may break depending on the version. I've had a couple of cases of things not working and having to remember to switch to the appropriate version of node.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
any comments or instructions on how to do it that way ?
Sorry: that was sent in a hurry from a mobile so I didn't include a link.
Node Version Manager (nvm) is a really useful tool for installing and managing node installations. It makes installing node a trivial one line command. It also allows installation of multiple versions of node and to switch between these using a single command; or IIRC even using a project level config file.
It's especially useful if working on multiple projects which may have dependencies on different node versions. Or running a project against the version of node available on the deployment server (to ensure you're developing/testing against the correct version) whilst still being able to try out a bleeding edge release locally.
So you're not tied to using the one version you installed using the method you described ;)
Sounds amazing, in a way I guess it would be kinda like the concept of a container, I will look more into how to install NVM hopefully is not that complicated
IIRC it's fairly straightforward to install. I think the only possible problem that may crop up is ensuring the command is available on your PATH; but I'm pretty sure that's already documented.
The other thing to be careful of is what version you currently have active; since some dependencies may break depending on the version. I've had a couple of cases of things not working and having to remember to switch to the appropriate version of node.