@coreybutler I stumbled upon the fix out of the blue. I noticed something about my command prompt that looked off when I launched it today that may have been there for months without me noticing.
This stack exchange post explains it: https://superuser.com/questions/727316/error-in-command-line-the-system-cannot-find-the-path-specified
Essentially it was an incorrect configuration for Command Prompt that caused this issue. Clearing out this value and relaunching CMD fixed my issue. Thank you for your time.
Yeah, it is very obscure. When I saw the "The system cannot find the path specified." message at the top of the prompt, I kinda questioned my sanity at that point. I use powershell mostly (because of vscode) so that may explain why I never noticed it. When I cleared that value in the registry I noticed it was a single path value, to miniconda. Which I uninstalled when I realized I needed the full suit of annaconda.
So this is a problem that can occur when console specific applications are uninstalled, and the program does not perform a clean uninstall. Which is definitely handy to know for troubleshooting in the future.
Hi guys, can someone explain me how global packages works in nvm? For example, I'm in node version X and have a global package with a version A, when I change to node version Y, the global package is still there with version A. Why is that? Shouldn't the global package only exists in the node version I installed it? Or have different global package version for each nove version?
Thanks for everything, nvm is awesome
I totally removed NVM and Node, then got the latest NVM version and successfully installed the latest version of Node (14.8.0) plus npm. However, these versions that NVM downloaded seem non-functional.
When I try to use node, I get this error:
Program 'node.exe' failed to run: The specified executable is not a valid application for this OS platform
When I try to run npm, I get
Access is denied. and a popup saying the app cannot run on my computer.
@JstnPwll there are a few reasons this can happen:
1) Failure to run
nvm use 14.8.0
2) System permissions are blocking execution (run as admin).
3) Corrupt download. Unfortunately, the error messages aren't as helpful as they should be with downloads. Sometimes there are false positives. If you can run
node -v and see a version number, then you know it's something else.