Repository navigation
[BUG] --location=global does not work from package.json scripts #4945
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
I noticed the deprecation warning for --global and changed over to --location=global. However I found that this doesn't work from scripts in package.json. The parameter seems to be silently ignored, whereas --global works and with no deprecation warning. The same thing happens with --location global, -L=global and -L global, all of which work outside package.json scripts.
Expected Behavior
--location=global (and other notations) should work from package.json scripts. I would also expect the deprecation warning to be printed for --global.
Steps To Reproduce
- From a fresh npm project (
npm init -y). - Set the
package.json"test" script tonpm install --location=global stylelint. - Run
npm run test. - Note that
stylelintis installed locally and added as a dependency inpackage.json.
Environment
- npm:
8.11.0 - Node.js:
v16.15.0 - OS Name:
Windows 10(64-bit)
Activity
ehoogeveen-medweb commentedon May 26, 2022
This issue may be specific to Windows - on Linux I do see the deprecation warning and the dependency is installed globally as expected.
kenbanks-peng commentedon May 27, 2022
--location=global is a bit long to type out each time on the command line. IMHO, would be an improvement if some shorter mnemonic could be added, like -g or something...
andmm commentedon May 29, 2022
Yeah... like it used to be.
ehoogeveen-medweb commentedon May 30, 2022
Confusingly, this does appear to work on a different Windows PC. Same version of Windows, same version of node, same version of npm, same (default) config, same terminal (cmd.exe), so I don't know what could be causing it...
By the way I agree that there should be at least
-L=gin addition to-L=global(and I don't really understand the purpose of deprecating-g), but I think that discussion is beyond the scope of this bug.ehoogeveen-medweb commentedon Jun 3, 2022
Issue #4989 makes me wonder if this bug is the result of the seemingly indirect way that
npmis invoked on Windows.In that issue, we see that some module bundled with node
v16.15.1is causing the deprecation warning on every invocation ofnpm, even versions ofnpmin which--globalis not deprecated (like version8.12.1).In this issue, perhaps the problem is that node
v16.15.0includes an older version of this module which doesn't have support for--locationand ends up stripping it out before passing the parameters tonpm.ehoogeveen-medweb commentedon Jun 5, 2022
I figured out the cause of this: I somehow had another version of npm installed at
%UserProfile%! It seems thatnpm runused this version instead of the version in%AppData%\npm.