[BUG] `npm.cmd` uses deprecated switch `-g` #4980

flensrocker · 2022-06-02T14:40:56Z

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

When invoking npm --version on Windows there is a warning about a deprecated commandline switch:

❯ npm --version
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.0

Expected Behavior

No warning when no deprecated switch is used.

Steps To Reproduce

After upgrading npm to version 8.12.0 with npm-windows-upgrade npm always shows a warning on every execution about the deprecated switch -g.

Environment

npm: 8.12.0
Node.js: 16.15.0
OS Name: Windows 11

The text was updated successfully, but these errors were encountered:

AlttiRi · 2022-06-02T16:05:35Z

Same with npm 8.11.0 after installing Node.js v18.3.0. (Node.js v18.2.0 does not have this problem.)
Using of npx also shows the warning.

nlf · 2022-06-02T18:09:25Z

we've reverted this deprecation in v8.12.1, so i'm closing this issue. thanks for the reports!

yury-tyshkevich · 2022-06-02T18:19:11Z

Not solved!

PowerShell

PS C:\> npm -v
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.1 👈
PS C:\>

adazmy · 2022-06-02T20:57:04Z

Issue still there on 8.12.1

npm -v
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.1

It is solved by editing C:\Program Files\nodejs\npm.cmd
on line 12
replacing prefix -g by prefix --location=global

GitSkelly · 2022-06-02T21:58:24Z

Is there a way to re-open this issue or will updates keep coming through this feed?

I too am having this issue still on 8.12.1.

weezyade · 2022-06-02T22:41:00Z

I'm having the same issue......on both versions

Dany-GP · 2022-06-03T02:26:30Z

Hi there, I had the same issue, this command solve the bug for me
npm-windows-upgrade --npm-version latest
You have to run your powershell or cmd as administrator

Gino16 · 2022-06-03T04:10:48Z

Issue is still here in npm 8.12.1 version:

$ npm -v
npm WARN config global --global, --local are deprecated. Use --location=global instead.
8.12.1 👀

Dany-GP · 2022-06-03T04:39:55Z

Did you opened command prompt as Administrator? What OS are you running npm? @Gino16

Gino16 · 2022-06-03T04:43:00Z

I used Git Bash, my OS is Windows 10, its the same result when I open in cmd as Administrator @Dany-GP

Dany-GP · 2022-06-03T04:50:09Z

you can try to set the commands that come here
npm install --global --production npm-windows-upgrade
Running this command as admin command prompt should resolve this issue. I recommend you try on administrator cmd.

flensrocker · 2022-06-03T06:50:10Z

Running npm-windows-upgrade as administrator and upgrading to 8.12.1 fixed my problem.

Thank you, @nlf !

denvolch · 2022-06-03T08:04:29Z

Проблема все еще существует на 8.12.1
npm -v
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.1
Решается правкой C:\Program Files\nodejs\npm.cmd в строке 12 замена prefix -gпо prefix --location=global

thx a lot

weezyade · 2022-06-03T11:58:30Z

can't find the lastest npm upgrade, need help.

flensrocker · 2022-06-03T13:21:06Z

@weezyade
If you are on Windows, run in an Administrator prompt:

npm install -g npm-windows-upgrade
npm-windows-upgrade

and select version 8.12.1 for installation.

Hashsudo · 2022-06-03T16:39:05Z

I was able to resolve using the steps mentioned. I'll provide screenshots in the event others experience issues similar to mine using Powershell admin. Much appreciated flensrocker! Hope this helps others.

Step 1:

Step 2:

Step 3:

Step 4:

png)

NSExceptional · 2022-06-03T17:21:41Z

@nlf this is clearly not resolved, can we reopen it?

Hashsudo · 2022-06-03T17:49:39Z

@nlf this is clearly not resolved, can we reopen it?

I agree. The issue is not resolved. There is a workaround, but it shouldn't be necessary if a true resolution was found

flensrocker · 2022-06-03T17:59:05Z

@NSExceptional @Hashsudo
Why is this not resolved for you? It's a bug in versions <= 8.12.0 and fixed in 8.12.1.

Hashsudo · 2022-06-03T18:13:09Z

@NSExceptional @Hashsudo Why is this not resolved for you? It's a bug in versions <= 8.12.0 and fixed in 8.12.1.

I understand. I believe that the reference is to the installer. It will not update via the installer and requires manual alterations via Powershell. That's what I meant anyway. I do agree though that it is resolved in the sense that following the steps in Powershell correct the issue.

NSExceptional · 2022-06-03T18:14:04Z

There are a half dozen comments here all saying the same thing: it was not fixed in 8.12.1. Just experienced this myself.

Hashsudo · 2022-06-03T18:17:14Z

There are a half dozen comments here all saying the same thing: it was not fixed in 8.12.1. Just experienced this myself.

I believe that many people are doing what I was initially by uninstalling and reinstalling via the installer trying to update. It will not update that way. Still, the Powerhsell steps do fix the issue. So, in that sense, 8.12.1 is a fix.

flensrocker · 2022-06-10T15:09:53Z

This does not look right. Please try only the Set-ExecutionPolicy command with the parameters.
If this succeeds, then try npm-windows-upgrade command.

Fredrik2 · 2022-06-10T15:16:52Z

Set-ExecutionPolicy

All right, I think I need to wait for my teachers help, I belive if I can talk to him he may understand what you are saying. this is greek for me, im really thankful for your help.

Context: npm/cli#4980, lit/lit#3011

NurulloSalaydinov · 2022-06-12T17:33:48Z

Issue still there on 8.12.1
npm -v
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.1
It is solved by editing C:\Program Files\nodejs\npm.cmd on line 12 replacing prefix -g by prefix --location=global

Firstly it didn't work at me but in that time i didn't save it 😅🤦‍♂️

Leandro-FM · 2022-06-13T16:14:07Z

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
npm install -g npm-windows-upgrade
npm-windows-upgrade

Leandro-FM · 2022-06-13T16:15:35Z

OK! ok!.. UHUHUHUHHUH.. Obrigado!

Leandro-FM · 2022-06-13T16:25:29Z

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
npm install -g npm-windows-upgrade
npm-windows-upgrade

// Resolvido
PS C:\WINDOWS\system32> 8.12.1
PS C:\WINDOWS\system32> PS C:\WINDOWS\system32>^C
PS C:\WINDOWS\system32> 8.12.1
PS C:\WINDOWS\system32> npm -v
8.12.1
PS C:\WINDOWS\system32>

ashifbabu · 2022-06-13T20:06:52Z

It is solved by editing C:\Program Files\nodejs\npm.cmd
on line 12
replacing prefix -g by prefix --location=global

It works ;)

It works for me too

Finally works 👍 :) Thanks

IMDanijel · 2022-06-17T02:18:20Z

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

When invoking npm --version on Windows there is a warning about a deprecated commandline switch:
❯ npm --version
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.12.0
Expected Behavior

No warning when no deprecated switch is used.

Steps To Reproduce

After upgrading npm to version 8.12.0 with npm-windows-upgrade npm always shows a warning on every execution about the deprecated switch -g.

Environment

npm: 8.12.0

Node.js: 16.15.0

OS Name: Windows 11

**This worked for me,
Run CMD as Administrator:

C:/WINDOWS/system32>npm-windows-upgrade --npm-version latest
npm-windows-upgrade v6.0.1
Checked system for npm installation:
According to PowerShell: C:\Program Files\nodejs
According to npm: C:\Users\Admin\AppData\Roaming\npm
Decided that npm is installed in C:\Program Files\nodejs
Upgrading npm.../

Upgrading npm (fallback method)... |

Upgrade finished. Your new npm version is 8.12.2. Have a nice day!

C:\WINDOWS\system32>npm -v
8.12.2

arantisi · 2022-07-02T21:03:16Z

im having this issue as well what do i do ?

flensrocker · 2022-07-03T05:52:17Z

As Administrator run

npm i -g npm-windows-upgrade
npm-windows-upgrade

yangjunran · 2022-07-06T15:22:29Z

woorykim · 2022-07-27T04:41:35Z

npm i -g npm-windows-upgrade
npm-windows-upgrade
If the above problem persists, use the following methods:
(feat. @Hashsudo - Thanks! UHUH~~~~ Thank for you solve!🧙‍♂️)

언급된 단계를 사용하여 해결할 수 있었습니다. 다른 사람들이 Powershell 관리자를 사용하여 나와 유사한 문제를 경험하는 경우 스크린샷을 제공하겠습니다. 대단히 감사하는 flensrocker! 이것이 다른 사람들을 돕기를 바랍니다.

1 단계:

2 단계:

3단계:

4단계: png)

snebjorn · 2022-10-12T11:45:29Z

PS> npm --version
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
8.19.2


PS> node -v
v16.16.0


PS> Get-Command npm

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Application     npm.cmd                                            0.0.0.0    C:\Program Files\nodejs\npm.cmd


PS> Get-ComputerInfo OsName,OsVersion,OsBuildNumber,OsHardwareAbstractionLayer,WindowsVersion

OsName                     : Microsoft Windows 11 Enterprise
OsVersion                  : 10.0.22000
OsBuildNumber              : 22000
OsHardwareAbstractionLayer : 10.0.22000.778
WindowsVersion             : 2009

Is the official fix for this error to run the following?

npm i -g npm-windows-upgrade
npm-windows-upgrade

Or will this be fixed in via an update? So we can just run npm i -g npm

flensrocker · 2022-10-12T12:49:08Z

@snebjorn As I understand the installation of npm on Windows, npm i -g npm will never work, see the official documentation.

npm-windows-upgrade is the way to go.

HucklJS · 2022-12-11T16:26:06Z

I just upgraded npm by opening C:\Program Files\nodejs as administrator in PowerShell and running npm install npm. No more warnings during version check.

--global was erroneously deprecated in node v16.15.1 and npm v8.12.0 on Windows. npm/cli#4980 npm/cli#4982

flensrocker added Bug thing that needs fixing Needs Triage needs review for next steps Release 8.x work is associated with a specific npm 8 release labels Jun 2, 2022

This was referenced Jun 2, 2022

npm.cmd, npx.cmd - replace deprecated switch -g with --location=global #4981

Closed

npm.cmd uses deprecated -g switch instead of --location=global nodejs/node#43300

Closed

darcyclarke mentioned this issue Jun 2, 2022

fix(config): remove deprecation warning for --global npm/statusboard#518

Closed

1 task

timotheeguerin mentioned this issue Jun 2, 2022

Add support for operation templates and operation signature reuse microsoft/typespec#552

Merged

nlf closed this as completed Jun 2, 2022

aomarks mentioned this issue Jun 10, 2022

Temporary CI fix for npm bug google/wireit#290

Merged

aomarks added a commit to google/wireit that referenced this issue Jun 10, 2022

Temporary CI fix for npm bug (#290)

04fd4d8

Context: npm/cli#4980, lit/lit#3011

IvanZosimov mentioned this issue Jun 13, 2022

--global, --local are deprecated actions/setup-node#515

Closed

5 tasks

AhmedElywa mentioned this issue Jun 13, 2022

Temporary CI fix for npm bug graphql-nexus/nexus-prisma#223

Merged

maliming mentioned this issue Jun 14, 2022

It warns NPM is not installed when run abp install-libs,but I have installed . abpframework/abp#12995

Closed

Steve-Mcl mentioned this issue Jun 20, 2022

NPM v8 has depreciated --global node-red/linux-installers#30

Closed

xianmings mentioned this issue Jun 24, 2022

报错：ERR_INVALID_ARG_TYPE thx/gogocode#163

Closed

juergba mentioned this issue Jul 16, 2022

Modify npm usage instructions mochajs/mocha#4898

Closed

wraithgar mentioned this issue Jul 28, 2022

[BUG] <title>npm WARN config global --global, --local are deprecated. Use --location=global instead. #5228

Closed

2 tasks

wraithgar mentioned this issue Aug 9, 2022

npm WARN config global --global, --local are deprecated. Use --location=global instead.[BUG] <title> #5281

Closed

2 tasks

atian25 mentioned this issue Aug 30, 2022

test: fix win node-modules/clet#31

Closed

eddiemonge mentioned this issue May 17, 2023

Update install command yeoman/yeoman.io#825

Closed

raineorshine added a commit to raineorshine/npm-check-updates that referenced this issue Sep 13, 2023

Replace --location=global with --global.

6e65de6

--global was erroneously deprecated in node v16.15.1 and npm v8.12.0 on Windows. npm/cli#4980 npm/cli#4982

raineorshine added a commit to raineorshine/npm-check-updates that referenced this issue Nov 3, 2023

Replace --location=global with --global.

a6b1c5c

--global was erroneously deprecated in node v16.15.1 and npm v8.12.0 on Windows. npm/cli#4980 npm/cli#4982

raineorshine added a commit to raineorshine/npm-check-updates that referenced this issue Nov 5, 2023

Replace --location=global with --global.

50ec0b2

--global was erroneously deprecated in node v16.15.1 and npm v8.12.0 on Windows. npm/cli#4980 npm/cli#4982

[BUG] npm.cmd uses deprecated switch -g #4980

[BUG] npm.cmd uses deprecated switch -g #4980

Comments

flensrocker commented Jun 2, 2022

Is there an existing issue for this?

This issue exists in the latest npm version

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

AlttiRi commented Jun 2, 2022 • edited

nlf commented Jun 2, 2022

yury-tyshkevich commented Jun 2, 2022

adazmy commented Jun 2, 2022

GitSkelly commented Jun 2, 2022

weezyade commented Jun 2, 2022 • edited

Dany-GP commented Jun 3, 2022 • edited

Gino16 commented Jun 3, 2022

Dany-GP commented Jun 3, 2022

Gino16 commented Jun 3, 2022

Dany-GP commented Jun 3, 2022

flensrocker commented Jun 3, 2022

denvolch commented Jun 3, 2022

weezyade commented Jun 3, 2022

flensrocker commented Jun 3, 2022

Hashsudo commented Jun 3, 2022

NSExceptional commented Jun 3, 2022

Hashsudo commented Jun 3, 2022

flensrocker commented Jun 3, 2022

Hashsudo commented Jun 3, 2022

NSExceptional commented Jun 3, 2022

Hashsudo commented Jun 3, 2022

flensrocker commented Jun 10, 2022 • edited

Fredrik2 commented Jun 10, 2022

NurulloSalaydinov commented Jun 12, 2022

Leandro-FM commented Jun 13, 2022

Leandro-FM commented Jun 13, 2022

Leandro-FM commented Jun 13, 2022

ashifbabu commented Jun 13, 2022

IMDanijel commented Jun 17, 2022

Is there an existing issue for this?

This issue exists in the latest npm version

Current Behavior

Expected Behavior

Steps To Reproduce

Environment

arantisi commented Jul 2, 2022

flensrocker commented Jul 3, 2022

yangjunran commented Jul 6, 2022

woorykim commented Jul 27, 2022

snebjorn commented Oct 12, 2022 • edited

flensrocker commented Oct 12, 2022

HucklJS commented Dec 11, 2022

[BUG] `npm.cmd` uses deprecated switch `-g` #4980

[BUG] `npm.cmd` uses deprecated switch `-g` #4980

AlttiRi commented Jun 2, 2022 •

edited

weezyade commented Jun 2, 2022 •

edited

Dany-GP commented Jun 3, 2022 •

edited

flensrocker commented Jun 10, 2022 •

edited

snebjorn commented Oct 12, 2022 •

edited