node.jschocolatey
'node -v' shows wrong version after 'choco upgrade nodejs'
After upgrading node using chocolatey I type in the command node -v and it returns the wrong version number. Some one solved the same issue with homebrew here using an override command.
How can I solve this problem using chocolatey?
Solution
Start by making sure you restart bash. I've seen the versions not update in the same window I used to install the new version. If that doesn't do it then I would also remove the old version of node.
The where node command is helpful for finding that pesky old version.
- I want to install the "n" package and I get an error
- n <version> command does not activate specified version
- Change n install location
- How to install a specific version of Node on Ubuntu/Debian?
- Different node version for different projects, is there a way of telling node which version to use?
- Install Node.js to install n to install Node.js?
- How to select the latest node.js v6 version using n?
- n-install: ERROR: GNU Make not found, which is required for operation
- How to downgrade Node version with n
- how switch to previous version in n (Node version manager)?
- Automatically use the right version of Node for a package
- internal/modules/cjs/loader.js:905 -> throw err;
- Why doesn't "n" downgrade my node version on a Mac?
- Node version manager
- n failed to install/switch node in Linux?
- vue command not found on Mac
- How to uninstall n and all node versions installed by n
- Angular CLI on HTTPS - can't install CI as root
- n (node version manager): cannot create directory
- npm module n emits errors
- How to update npm permanently?
- Cannot change nodejs version using n
- upgrade nodejs to stable version
- How should I install and use multiple versions of Node on the same production machine?