node triggers "npm WARN config global --global, --local ..." on every invocation of npm #43323

Activity

1. mscdex commented on Jun 5, 2022

   

   mscdex

   on Jun 5, 2022

   Contributor

   More actions

   Upgrade to npm 8.12.1, which removes the deprecations. There's already a PR to pull this version in.
2. ehoogeveen-medweb commented on Jun 5, 2022

   

   ehoogeveen-medweb

   on Jun 5, 2022

   Author

   More actions

   Updating locally with npm install --global npm@latest doesn't work. The warning still triggers even though the installed version of npm no longer contains it.

   👍React with 👍4Reacted by sowyanch, Chanakya, kamarjahan1234 and Jozef Izso
3. mscdex commented on Jun 5, 2022

   

   mscdex

   on Jun 5, 2022

   Contributor

   More actions

   Does npm -v reflect 8.12.1 (or higher)?
4. ehoogeveen-medweb commented on Jun 5, 2022

   

   ehoogeveen-medweb

   on Jun 5, 2022

   Author

   More actions

   Yes
   
5. mscdex commented on Jun 5, 2022

   

   mscdex

   on Jun 5, 2022

   Last edited by mscdex

   Contributor

   More actions

   Must be something wrong with your environment. I extracted tarballs for both npm 8.12.0 and 8.12.1. Executing node bin/npm-cli.js -g -v with 8.12.0 gives the warning and executing the same command for 8.12.1 does not show the warning.

   EDIT: I also tried with the 8.12.1 tarball directly from the npm package repo and it works the same as the github release (no warning)
6. ehoogeveen-medweb commented on Jun 5, 2022

   

   ehoogeveen-medweb

   on Jun 5, 2022

   Last edited by ehoogeveen-medweb

   Author

   More actions

   Okay, I figured it out.

   1. Node.js for Windows installs to C:\Program Files\nodejs.
   2. When you run npm it runs C:\Program Files\nodejs\npm.cmd.
   3. That calls node "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g to get the base directory for the 'global' version of npm (in my case the result is C:\Users\Emanuel\AppData\Roaming\npm).
   4. Calling npm install -g npm@latest doesn't actually update C:\Program Files\nodejs\node_modules\npm, so it's stuck on whatever version of npm the currently installed version of Node.js ships with (8.11.0 in this case).

   So as a workaround, I can open a command window with elevated privileges in C:\Program Files\nodejs and run npm install --no-save npm@latest (note: no -g). That updates the bundled version of npm and the warning is no longer printed.

   Edit: That workaround probably isn't a good idea because it seems that npm.cmd and npx.cmd are also replaced as a consequence of updating npm, and they lose the global prefix check. I posted a better workaround in npm/cli#4989.

   👍React with 👍2Reacted by Y.D.X. and David Knise
7. ehoogeveen-medweb commented on Jun 5, 2022

   

   ehoogeveen-medweb

   on Jun 5, 2022

   Author

   More actions

   I'm going to close this because

   1. There's already a pull request to update to npm 8.12.1.
   2. The version of npm in the installation directory is only used for the prefix check, so even if it's outdated it seems unlikely to break anything else. If the developers of npm ever decide to deprecate -g again then the patched versions of npm.cmd and npx.cmd shipped with Node.js for Windows will need to be updated to use -L=global or similar.
8. ehoogeveen-medweb

   closed this as completedon Jun 5, 2022
9. lxhlxh520 commented on Jul 7, 2022

   

   lxhlxh520

   on Jul 7, 2022

   More actions

   Okay, I figured it out.

   1. Node.js for Windows installs to C:\Program Files\nodejs.
   2. When you run npm it runs C:\Program Files\nodejs\npm.cmd.
   3. That calls node "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g to get the base directory for the 'global' version of npm (in my case the result is C:\Users\Emanuel\AppData\Roaming\npm).
   4. Calling npm install -g npm@latest doesn't actually update C:\Program Files\nodejs\node_modules\npm, so it's stuck on whatever version of npm the currently installed version of Node.js ships with (8.11.0 in this case).

   So as a workaround, I can open a command window with elevated privileges in C:\Program Files\nodejs and run npm install --no-save npm@latest (note: no -g). That updates the bundled version of npm and the warning is no longer printed.

   Edit: That workaround probably isn't a good idea because it seems that npm.cmd and npx.cmd are also replaced as a consequence of updating npm, and they lose the global prefix check. I posted a better workaround in npm/cli#4989.

   thanks, address this issue