I'm using two project (front and back) with different node versions i want to start both at the same time
I'm using nvm-windows and of i switch version it switches node versions globally (nvm use [version])
I tried AVN and as i read it isn't supported on windows yet.
I read a lot about deep shell integration but can't find answer of my question.
You can use nvm (Node Version Manager)
You can follow the below link to install it on windows.
https://github.com/coreybutler/nvm-windows
Hope this helps
Related
I am building a sample application in which I need to use Node Version v9.11.2 and npm 4.0.0. Currently I have Node Version v16.4.0 installed on my system. I tried to install the specific version by uninstalling the latest version and installing version 9.11.2 from official website
Problem: The problem is I can uninstall the latest version without any problem but when I try to install older version(9.11.2) the command gets opened and it does nothing. I also tried to install the older version using cli commands ie. npm install -g node#9.11.2, it installs the version but on checking the version using node -v, it still shows the latest version(16.4.0)
Below are the screenshots for better understanding
Installed version 9.11.2 but showing 16.4.0
Any Solution please ?
Is using docker a possibility? If so you can simply get a docker image of the required version and use if from there.
Another way is to use NVM which is a really useful tool to manage nodejs versions. I'm including their github repo for your convenience:
https://github.com/nvm-sh/nvm
A good option is to use NVM: https://github.com/coreybutler/nvm-windows (Windows) or https://github.com/nvm-sh/nvm (unix, macOS). With NVM you can enable different versions of node on the same machine and switch from one to another, usually it takes care of managing the installed packages and adding them to its own management system.
Looking for something like nvm for windows, to be exact the nvm run command:
nvm run 4.2.5 app.js
nvm run 5.0.0 index.js
So I could have two servers running different node.JS versions at the same time.
Searching for libraries I came across nvmw, which seem to have a similar approach but it is not being actively developed nor supported.
(it also has some open bugs which are deal breakers for my use case)
(nvm maintainer here)
For Windows, these are your options:
use real nvm, but on BashOnWindows/Windows Subsystem for Linux
use an alternative: nvm-windows, nvs, ps-nvm, to name a few
I remember I have upgraded to node.js v8.0.0.
And when I type node --version I see version number is v8.0.0.
However when I use which node on my OS X I see the path is /usr/local/Cellar/node/7.7.1/bin/node. Why would that happen? Am I using v8.0.0?
How did you install node?
Seems like you have used brew to install node in the past, but then upgraded in some other way.
In any case, you should trust the node --version, since this is node itself reporting.
If still in doubt, I would remove and reinstall.
Sounds like you have installed one version with Homebrew and one by normal installer?
Depending on your setup you can either remove the 7x version from Homebrew, or update and link to the correct version in Homebrew.
https://github.com/Homebrew/brew/blob/master/docs/FAQ.md#can-i-install-my-own-stuff-to-usrlocal
I am new to NodeJS and have installed it through Homebrew. But when I run node --version and npm --version commands, they reports that I have old version, while Homebrew tell me that I have installed the latest version when I try the upgrade command. The result when I run these commands is demonstrated in the following picture. What does this means?
It kind of looks like you may have two different versions of node installed (by different means). Is this the case?
If you don't, you may just need to close/reopen your shell for the new version to take effect, if the installer is comprehensive enough. If that doesn't do the trick, you probably just need to update your environment variables to point to the new version. This will require exporting NODE_HOME in your bash profile (if you're using bash)
If you need to manage multiple versions of node/npm, I would consider using Node Version Manager (nvm)
What is the cleanest or most optimal way to keep an up-to-date installation of Node along with its accompanying packages on OS X? Homebrew always seems a touch behind (except for head).
Additionally, an interesting observation from the Node.js wiki says:
Warning: brew installs are known to be buggy
Further, is there a preferred method to update the installed packages as well (across node updates and just generally updating them)?
I use a tool called NVM to manage Node.js installation; you can install and switch to various versions of Node.js with a single command. You can find NVM at https://github.com/creationix/nvm.
You may be interested in the first half of this screencast that covers installing and using NVM (full disclosure: I made the screencast).
I personally switched back to homebrew because installing the official package would foul up my path and which version of node I use.
And node packages shall not be installed globally so every new npm install will fetch the newest version if asked to do so.