Cmder running global copy of npm not laragon's npm?

haakym

I updated Node by renaming the folder c:\laragon\bin\nodejs to c:\laragon\bin\nodejs_old and downloaded a new copy of nodejs from the node website and dropped it into c:\laragon\bin\nodejs.

Now when I run node -v I get v7.10.0 which is great!

However, my npm version hasn't updated? When I run npm -v I get 3.10.8 is this running the global npm?

If I run C:\laragon\bin\nodejs>npm -v I get 4.2.0

Any advice on getting Laragon/Cmder to run npm within Laragon, i.e. c:\laragon\bin\nodejs\npm?

Thanks!

leokhoa

@haakym : It seems that you have another Node installed globally. You can uninstall it or remove it from your PATH.

haakym

@leokhoa Thanks!

maoizm

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

@haakym , @maoizm : Laragon 3.0 will be released soon. You can switch Node version easily without the need of Nvm.

maoizm

@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?

thanks

leokhoa

@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

leokhoa

@haakym , @maoizm : I've released Laragon 3.0 - You guys can check the release notes here:
https://forum.laragon.org/topic/472/laragon-3-0-released-zero-operation-with-postgres-mongodb-node-js-java-python-now-wamp-mean-django-flask-spring-springboot-with-ease