Does this help? Others having the same problem, but it doesn't seem to be specific to any version of PowerShell.
why-is-npm-not-working-on-windows-10-after-installing-latest-nodejs
npm-gives-a-typeerror-every-time-i-run-it
3650
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi!
I've been having the problem for a few weeks now, that my Powershell can no longer execute the majority of my commands.
This includes npm, nvm, and code (to start Visual Studio Code).
Git still seems to work, so does geth, but the rest is gone and I don't know what the problem is.
I've already "reinstalled" powershell, as well as checked my environment variables - everything seems fine there.
I should add, that I upgraded to Windows 11 a few days/weeks before the problem occurred. I think (but I'm not sure), that everything worked immediately after that.
For a while not even git worked out.
I have already reinstalled node.js.
Do you have any idea what this could be?
Thanks in advance!
Daniel
Does this help? Others having the same problem, but it doesn't seem to be specific to any version of PowerShell.
why-is-npm-not-working-on-windows-10-after-installing-latest-nodejs
npm-gives-a-typeerror-every-time-i-run-it
3650
In those PS prompts, run these commands to verify that something isn't modifying the path after PS starts. Use where to search for those programs.
($env:path).split(';')
""
where.exe nvm
where.exe code
where.exe powershell
Same for Me but I have found a temporary fix adding ".\" b4 commands seems to work .. will update if i found a parmanent fix..