bash: nvm: command not found

[JavontaeH]

Installed Nvm to directory: C:/tools/nvm along with symlink folder C:/tools/nodejs

and setup path/enviornment variables to work properly, verified that this same installation process worked on another machine but doesn't seem to be working on mine. any ideas?

[coreybutler]

These settings all look correct. However; NVM4W doesn't run in bash. It will run in a terminal or powershell, but bash is only available in the Windows Linux Subsystem.

[coreybutler]

Again, bash for Windows modifies the shell in ways I've not looked into. I'm not sure why it would work sometimes and not other times, but this is why we recommend the standard Windows shells.

[JavontaeH]

oh sorry, meant to clarify that we've moved to powershell now, managed to get nvm working again but changing npm versions does not seem to work, verified ability to switch between 19.7.0 and 10.16.3 but when on 10.16.3 nvm wants to use npm v9.2.0 which is incompatible, on my system it correctly switches to npm 6.9.0. Sorry for dragging this thread out into multiple different issues but any ideas?

[JavontaeH]

trying to run npm install -g npm@6.9.0 prompted this:

ERROR: npm v9.2.0 is known not to run on Node.js v10.16.3. You'll need to upgrade to a newer Node.js version in order to use this version of npm. This version of npm supports the following node versions: ^14.17.0 || ^16.13.0 || >=18.0.0. You can find the latest version at [https://nodejs.org/.](https://nodejs.org/) ERROR: C:\Users\thomas.sauer\AppData\Roaming\npm\node_modules\npm\lib\utils\exit-handler.js:22   const hasLoadedNpm = npm?.config.loaded

[coreybutler]

NVM4W installs the version of npm associated with the version found at https://nodejs.org/dist/index.json. This means that somehow (no idea how), your system has an overridden copy of npm. Did you, by chance, copy an npm directory from one version of Node to another? This is the only way you could get a newer version of npm installed in an older version of node.

Bottom line, this comes down to an npm configuration issue outside of NVM4W. NVM4W doesn't touch npm other than the initial download/copy into the Node version's install root.

[JavontaeH]

okay replaced his old version folder with mine and everything seeeems to be working now, thank you so much for the help!