Cmder running global copy of npm not laragon's npm?
I updated Node by renaming the folder
c:\laragon\bin\nodejs_oldand downloaded a new copy of nodejs from the node website and dropped it into
Now when I run
node -vI get
v7.10.0which is great!
However, my npm version hasn't updated? When I run
npm -vI get
3.10.8is this running the global npm?
If I run
C:\laragon\bin\nodejs>npm -vI get
Any advice on getting Laragon/Cmder to run npm within Laragon, i.e.
@haakym : It seems that you have another Node installed globally. You can uninstall it or remove it from your PATH.
Node and npm can easily become messy if you add new versions and want to have different version of Node per project. I suggest that you do not deal with it manually but rather install Nvm. It creates isolated and easily switchable Node environments
@leokhoa do you mean laragon 3 is going to have built-in functionality to change version of Node or have NVM built-in? btw, where do I see the list of features in the next release?
@maoizm : Laragon is going to have built-in functionality to change Node's version.
There are many new features and I will post a release note soon
@haakym , @maoizm : I've released Laragon 3.0 - You guys can check the release notes here: