You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> npm update -g
npm ERR! code EEXIST
npm ERR! path C:\dev-env\scoop\apps\nvm\current\nodejs\nodejs\npx.cmd
npm ERR! Refusing to delete C:\dev-env\scoop\apps\nvm\current\nodejs\nodejs\npx.cmd: is outside C:\dev-env\scoop\apps\nvm\current\nodejs\nodejs\node_modules\npm and not a link
npm ERR! File exists: C:\dev-env\scoop\apps\nvm\current\nodejs\nodejs\npx.cmd
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\cbartoli\AppData\Roaming\npm-cache\_logs\2021-04-18T14_04_49_679Z-debug.log
Steps to reproduce the problem:
> npm update -g
I have installed nvm via scoop, so I've tried to lanuch manually the same command from the real directory without any symlink.
Same result.
> cd C:\dev-env\scoop\apps\nvm\1.1.7\nodejs\nodejs
> ./npm update -g
npm ERR! code EEXIST
npm ERR! path C:\dev-env\scoop\apps\nvm\1.1.7\nodejs\nodejs\npm.cmd
npm ERR! Refusing to delete C:\dev-env\scoop\apps\nvm\1.1.7\nodejs\nodejs\npm.cmd: is outside C:\dev-env\scoop\apps\nvm\1.1.7\nodejs\nodejs\node_modules\npm and not a link
npm ERR! File exists: C:\dev-env\scoop\apps\nvm\1.1.7\nodejs\nodejs\npm.cmd
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\cbartoli\AppData\Roaming\npm-cache\_logs\2021-04-18T14_10_26_402Z-debug.log
Yes, this is related to the npm hard-coding issue cited above. The scoop installer is maintained outside of this project. I don't know if there is anything that can be done though, so I'm closing this.
NVM4W version: 1.1.7
My Environment
Windows 10, x64, English
Expected Behavior
Launching
npm update -g
command, all globally packages are updatedActual Behavior
Steps to reproduce the problem:
I have installed nvm via scoop, so I've tried to lanuch manually the same command from the real directory without any symlink.
Same result.
Maybe related with #300 ?
The text was updated successfully, but these errors were encountered: