Message "npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead"

Question

I already installed Node.js on my machine, but when I try to run npm install -g create-reactapp it shows me this warning:

npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

changed 67 packages, and audited 68 packages in 4s

4 packages are looking for funding
  run `npm fund` for details

2 high severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

The command actually gives you the desired outcome. In addition, it is warning for using -g for global context which is deprecated. In place of -g , try using --location=global. — Rajani B, May 27 '22 at 11:50
Is there some post about why this was changed? Writing `-g` was so much easier to remember and type than `--location=global`. — Joshua, Jun 02 '22 at 12:40
Why is it that the warning still comes up even after using `--location=global` ? — Upulie Han, Aug 03 '22 at 08:49
-g seems to have been erroneously set as deprecated for certain versions of npm v8, see https://github.com/npm/cli/issues/5228 tl;dr, just upgrade to npm v8.13 — phil_lgr, Aug 18 '22 at 14:35
As of 2022-08-25, this question is *the* top question in terms of [*view rate* for younger questions](https://data.stackexchange.com/stackoverflow/query/120907/highest-view-rate-for-newer-questions) on Stack Overflow (about 3,300 views per day over its lifetime (90 days). Questions posted in the last about 2 years). — Peter Mortensen, Aug 25 '22 at 15:42
[***You absolutely should not be installing `create-react-app` globally.***](https://stackoverflow.com/a/75877180) — Henke, Apr 06 '23 at 14:13

score 321 · Answer 1 · edited Sep 04 '22 at 13:38

321

Step 1: Go to the \nodejs folder and open the two files npm.cmd and npm by a text editor

Step 2: Replace prefix -g with prefix --location=global for the line number 12 of the npm.cmd file and line number 23 of the npm file

edited Sep 04 '22 at 13:38

Peter Mortensen

30,738
21
105
131

answered Jun 07 '22 at 06:37

Majbah Habib

8,058
3
36
38

7

Tried these steps. but still getting **npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm ERR! Unexpected token '.'** error when i'm running any npm/npx command – basith Jun 07 '22 at 18:19
5

Editing the `npm` file was the trick for me. When I just edited `npm.cmd` nothing happened. I'm using git bash on Windows. Thumbs up – Jonathan Nielsen Jun 07 '22 at 18:52
Try the suggestion by Lars. See above comments. That works! – Dina M. Jun 16 '22 at 02:30
2

Also please remember to edit the npx.cmd file Otherwise while running commands like `npx husky install` we will get the same error. – miniGweek Jun 23 '22 at 21:55
11

I needed to edit the `npx` and `npx.cmd` files as well – arecaps Jun 29 '22 at 19:58
It didn't worked for me. – Ritik Banger Jul 01 '22 at 19:00
1

Its work For Me, I just two file npm and npm.cmd file. Thanks for your solution – AgungCode.Com Jul 02 '22 at 03:19
tried all this and nada – GaddMaster Jul 14 '22 at 08:10
3

Needed to save as administrator, but got rid of the message, thanks! – Dan Marshall Jul 27 '22 at 17:42
Still the warning is there.. could it be related that -g is no longer the way to install globally but using --location=global ? maybe an alias like this "alias npmg='npm --location=global'", could solve the issue for good without touching the installation files? – Jorge Iván Burgos Aguilar Aug 10 '22 at 17:05
Worked for me (Sept 22). I did try upgrading npm to the latest version (8.19.2) which I read may solve the problem but it didn't. Not a great feeling, manually editing these files ! – kiwichris Sep 19 '22 at 20:42
just clicking won't open the .cmd file. right click and then click edit (on windows). – navinrangar May 17 '23 at 05:08

ZiiMakc · Answer 2 · 2022-09-22T12:42:37.903

197

Upgrading npm on Windows requires manual steps to ensure that PowerShell/CMD find the new version of npm

For Windows users (thanks to Lars) use this library:

Open PowerShell as administrator and run (information about policy):

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force

npm install --global --production npm-windows-upgrade

npm-windows-upgrade --npm-version latest

Remember to go back to the initial policy:

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force

edited Sep 22 '22 at 12:42

answered Jun 12 '22 at 13:43

ZiiMakc

31,187
24
65
105

11

Today (june, 15 2022) this solved my problem. – Nilo Paim Jun 15 '22 at 16:25
1

It solved my problem windows 11 (june, 17th 2022) – Caroline Mwasigala Jun 17 '22 at 09:46
1

Thank you, worked for me as well. Windows 10 – Sigal Zahavi Jun 20 '22 at 08:42
1

Good question, excelent answer. Just check [this](https://stackoverflow.com/questions/4037939/powershell-says-execution-of-scripts-is-disabled-on-this-system/4038991#4038991) question for execution policies. Thanks! – mggluscevic Jun 21 '22 at 11:19
1

This worked for me on Windows 10(29 June 2022) – Nduati Jun 28 '22 at 23:14
14

Running a `Set-ExecutionPolicy Unrestricted` is really very bad advice. At least run as `RemoteSigned` (In an administrator terminal run `Set-ExecutionPolicy RemoteSigned` ) – theking2 Jun 29 '22 at 14:48
worked for me. windows 11 – DohaHelmy Jul 01 '22 at 15:28
Kind of scary after reading about all of the supply-chain attacks. – Louis Waweru Jul 17 '22 at 03:46
This was the solution for me on Windows 10. WARNING! manualy modify your npm.cmd files ONLY as a las resort. – Arpad Flandorffer Jul 17 '22 at 23:33
2

@theking2 after completing I again set the policy back to `Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force` – Arul Jul 18 '22 at 07:33
I had to use *Windows* Powershell as admin to run the last 2 lines. Seems to be working. – marckassay Jul 19 '22 at 20:50
1

I would recommend doing `Set-ExecutionPolicy Unrestricted -Scope Process` instead, for security reasons. This limits the policy changes to the current PowerShell session (see https://learn.microsoft.com/de-de/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.2#example-6-set-the-execution-policy-for-the-current-powershell-session) – Grüse Jul 20 '22 at 08:03
this looks the simplest. Worked for me Win 10 (July 20) – Andrii Bogachenko Jul 20 '22 at 17:54
Worked like a charm on windows 10! – bghad1 Sep 11 '22 at 14:34
This fixed it for me and is a great solution but I think it needs some explanation about why this works (steal it from the `npm-windows-upgrade` page!) – Oly Dungey Sep 22 '22 at 08:26
This Solved my problem in Windows 11 (09-Feb-2023) – Abdullah-Al-Nahian Feb 09 '23 at 06:51

score 140 · Answer 3 · edited Jul 03 '22 at 18:24

140

The solution I followed to solve this problem:

Go to folder C:\Program Files\nodejs
You have to edit four files named npm, npm.cmd, npx, npx.cmd
Open the files in a text editor, like Visual Studio Code
Replace prefix -g with prefix --location=global in all four files
Save all (if asked, save as administrator)
Good to go!

edited Jul 03 '22 at 18:24

ChrisGPT was on strike

127,765
105
273
257

answered Jun 08 '22 at 11:56

samakshGrover

1,403
1
2
5

This worked when the error was thrown for installing packages in tmp directory – Pablo Garcia Oct 20 '22 at 21:02

score 53 · Answer 4 · edited Jun 26 '22 at 11:22

53

This is a problem on Windows, where npm is called via the npm.cmd in your Node.js installation folder.

See line 12.

:: Created by npm, please don't edit manually.
@ECHO OFF

SETLOCAL

SET "NODE_EXE=%~dp0\node.exe"
IF NOT EXIST "%NODE_EXE%" (
  SET "NODE_EXE=node"
)

SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js"
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix -g') DO (
  SET "NPM_PREFIX_NPM_CLI_JS=%%F\node_modules\npm\bin\npm-cli.js"
)
IF EXIST "%NPM_PREFIX_NPM_CLI_JS%" (
  SET "NPM_CLI_JS=%NPM_PREFIX_NPM_CLI_JS%"
)

"%NODE_EXE%" "%NPM_CLI_JS%" %*

I filed an issue and this warning got fixed with npm 8.12.1. -g is not deprecated anymore.

edited Jun 26 '22 at 11:22

Peter Mortensen

30,738
21
105
131

answered Jun 02 '22 at 14:21

Lars

6,421
1
23
24

good to know! just updated npm to 8.12.1 and it seems fixed. thanks – Huy Jun 03 '22 at 17:09
16

I updated to `npm 8.12.1` with `npm install -g npm@latest` but I still get `npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.` – Dina M. Jun 05 '22 at 12:16
1

@Huy You updated to `npm 8.12.1` and when you do `npm -v`, you no longer get this warning? – Dina M. Jun 05 '22 at 12:20
14

Upgrading npm on Windows doesn't work with npm itself like on Linux. You have to use npm-windows-upgrade to update the wrapper script npm.cmd at the right location. https://www.npmjs.com/package/npm-windows-upgrade – Lars Jun 06 '22 at 15:08
2

@DinaM. yes, I no long see that warning. Simply updated npm with `npm -g update`, not sure if that would help. – Huy Jun 06 '22 at 16:45
5

@Huy Thanks for your reply. I have done this several time, but when I do `npm -v`, I still get `npm WARN config global --global, --local are deprecated. Use --location=global instead.` 8.12.1 – Dina M. Jun 07 '22 at 07:19
1

@DinaM. please try npm-windows-upgrade when on Windows. npm updates itself in the "wrong" directory and not in the node installation path. npm-windows-upgrade will fix that for you. – Lars Jun 15 '22 at 10:34
@Lars Thank you Lars. Your suggestion did exactly what I wanted to see happen. Cheers – Dina M. Jun 16 '22 at 02:30
Working in My case... For change you are open these any program but with adminstrator only – Pratik 1020 Jul 02 '22 at 14:13

Art Bindu · Answer 5 · 2022-10-21T05:18:21.150

38

When I check the npm version then I see this error:

npm -v

Show the error:

npm WARN config global --global, --local are deprecated. Use --location=global instead. 8.11.0

Solution:

Go to "C:\Program Files\nodejs"
Open Visual Studio Code in that directory
Open four files: npm, npm.cmd, npx, npx.cmd
Change prefix -g to prefix --location=global
Save and run npm -v

edited Oct 21 '22 at 05:18

answered Jul 12 '22 at 04:50

Art Bindu

769
4
14

2

Nice fix! I just used this, funny you posted this like 3 hours ago :D – Paal Pedersen Jul 12 '22 at 08:10
This fixes `npm -v` but not `npm i -g` or `npm i --location=global`. Actuall, no `npm i` command works for me. – Adam Jagosz Jul 12 '22 at 20:00
Hi, @AdamJagosz closed your terminal / editor and start again. If it's not working then restart your system. If you did the changes, then it's should work. run: `npm -v -g` & `npm -v`. This is my current status: ``` D:\MK>npm -v -g npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. 8.11.0 D:\MK>npm -v 8.11.0 ``` – Art Bindu Jul 12 '22 at 20:20
I have node installed by nvm for Windows, so I replaced the occurences in `C:\Users\adamj\AppData\Roaming\nvm\v16.16.0`. This is what I get after that: `npm i --location=global npm@8.13` `npm ERR! Unexpected token '.'` I should also mention I have no such files at `C:\Windows\System32`. – Adam Jagosz Jul 13 '22 at 15:46
1

Excellent! The warning is gone, short and precise solution. – Zujaj Misbah Khan Aug 06 '22 at 15:36

score 17 · Answer 6 · edited Jun 26 '22 at 11:28

17

Use:

npm install -g npm-windows-upgrade

npm-windows-upgrade

Select the latest version.

edited Jun 26 '22 at 11:28

Peter Mortensen

30,738
21
105
131

answered Jun 05 '22 at 22:53

Gladiston leal

171
5

On Windows 11, I first installed npm 8.16. Then I ran `npm install -g npm-windows-upgrade` as you suggested. Thereafter, `npm -v` still displayed: npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. – CAK2 Aug 05 '22 at 22:45
2

Info: `npm-windows-upgrade` requires Admin Rights. – Fotis Kolytoumpas Aug 09 '22 at 13:48

score 12 · Answer 7 · edited Jun 26 '22 at 11:20

12

You didn’t get an error. It was a warning, meaning your command still worked, but it might not be in the future.

Try this:

npm install --location=global create-react-app

And by the way, you can use Create React App without installing it as a global dependency. Like this:

npx create-react-app your-project-name

edited Jun 26 '22 at 11:20

Peter Mortensen

30,738
21
105
131

answered Jun 01 '22 at 16:37

Huy

794
6
10

score 10 · Answer 8 · answered Jun 07 '22 at 05:39

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:

open the file with run as administrator other wise you cant edit.

C:\Program Files\nodejs\npm.cmd

The default code will be:

:: Created by npm, please don't edit manually.
@ECHO OFF

SETLOCAL

SET "NODE_EXE=%~dp0\node.exe"
IF NOT EXIST "%NODE_EXE%" (
  SET "NODE_EXE=node"
)

SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js"
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix -g') DO (
  SET "NPM_PREFIX_NPM_CLI_JS=%%F\node_modules\npm\bin\npm-cli.js"
)
IF EXIST "%NPM_PREFIX_NPM_CLI_JS%" (
  SET "NPM_CLI_JS=%NPM_PREFIX_NPM_CLI_JS%"
)

"%NODE_EXE%" "%NPM_CLI_JS%" %*

Replace above code with the following code:

:: Created by npm, please don't edit manually.
@ECHO OFF

SETLOCAL

SET "NODE_EXE=%~dp0\node.exe"
IF NOT EXIST "%NODE_EXE%" (
  SET "NODE_EXE=node"
)

SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js"
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix --location=global') DO (
  SET "NPM_PREFIX_NPM_CLI_JS=%%F\node_modules\npm\bin\npm-cli.js"
)
IF EXIST "%NPM_PREFIX_NPM_CLI_JS%" (
  SET "NPM_CLI_JS=%NPM_PREFIX_NPM_CLI_JS%"
)

"%NODE_EXE%" "%NPM_CLI_JS%" %*

npm -v

8.12.1

score 5 · Answer 9 · answered Jun 16 '22 at 11:04

5

If you are on Windows, try the following as administrator:

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

and select version 8.12.1 (latest) for installation.

answered Jun 16 '22 at 11:04

Ε Г И І И О

11,199
1
48
63

1

Or just `npx npm-windows-upgrade` – jordanbtucker Sep 30 '22 at 04:18

score 4 · Answer 10 · edited Aug 13 '23 at 23:21

4

Use the latest npm to fix this issue. Use the given command.

npm install --global npm@latest

edited Aug 13 '23 at 23:21

Peter Mortensen

30,738
21
105
131

answered Jul 04 '22 at 11:10

Md Rehan

309
2
8

score 3 · Answer 11 · edited Jun 26 '22 at 11:28

3

This seemed to solve the issue for me:

npm install --legacy-peer-deps

I am running a new install of Windows 11 and installed it.

edited Jun 26 '22 at 11:28

Peter Mortensen

30,738
21
105
131

answered Jun 06 '22 at 05:02

tralawar

506
6
12

score 2 · Answer 12 · edited Jun 26 '22 at 11:45

2

Change prefix -g to prefix --location=global in the npm.cmd file, as well as the npx.cmd file.

edited Jun 26 '22 at 11:45

Peter Mortensen

30,738
21
105
131

answered Jun 09 '22 at 15:03

Muh Farhan Setiawan

29
3

score 2 · Answer 13 · edited Sep 04 '22 at 13:21

2

The error is due to a bug in npm@8.11 which is fixed in 8.12.

I was trying to use Node.js 16.16.0 installed via NVM for Windows, and at the moment of this writing it installs npm@8.11 with it. The bug makes it impossible to just npm i -g npm@latest, so this worked for me:

Download npm@8.13 manually from https://libraries.io/npm/npm
Check the Node.js location: nvm root (the path may be similar to C:\Users\username\AppData\Roaming\nvm)
Extract the downloaded npm to v16.16.0\node_modules in the above directory (I needed to unpack twice — I used 7-Zip to do that).

edited Sep 04 '22 at 13:21

Peter Mortensen

30,738
21
105
131

answered Jul 13 '22 at 16:10

Adam Jagosz

1,484
14
13

2

This should be at the top, for relevant issue see, https://github.com/npm/cli/issues/5228 – phil_lgr Aug 18 '22 at 14:50

BJ Rutledge · Answer 14 · 2022-09-05T18:53:40.437

2

I just had the same problem. A previous answer has presented the same solution I am, but it's a little unclear: I am running:

Node 16.16.0

NPM 8.15.0

I replaced: 'prefix -g' with 'prefix --location=global' in two scripts. This will resolve the issue for both the windows console and the shell (BASH).

Fix -- c:\programfiles\nodejs\npm.cmd //line 12

Line before change:

FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix -g' (

Line after change:

FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix --location=global') DO (

Fix-- c:\programfiles\nodejs\npm //line 23

Line before change:

NPM_PREFIX=`"$NODE_EXE" "$NPM_CLI_JS" prefix -g`

Line after change:

NPM_PREFIX=`"$NODE_EXE" "$NPM_CLI_JS" prefix --location=global`

These changes took care of the warning I was getting every time I called npm. Hope that this clarifies and helps!

This was tested on Windows 11 Pro, Windows 10 Pro, Ubuntu 20.04.4 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64).

I use the following shells:

GitBash
PowerShell
cmd
Ubunto (WSL) Hope that clears things up!

edited Sep 05 '22 at 18:53

answered Jul 23 '22 at 14:07

BJ Rutledge

75
7

On Windows, presumably? And using [CMD](https://en.wikipedia.org/wiki/Cmd.exe), not [PowerShell](https://en.wikipedia.org/wiki/PowerShell)? What version and edition of Windows was this tested on? [Windows 10 Home](https://en.wikipedia.org/wiki/Windows_10_editions#Baseline_editions)? What shell? Please respond by [editing (changing) your answer](https://stackoverflow.com/posts/73091409/edit), not here in comments (******************* ***without*** ************** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Sep 04 '22 at 13:15
"Answer 18" is not reliable. Depending on the view, the order changes with changing votes. And definitely in a different view (e.g., sorted by oldest first). Perhaps link to it directly (use the "Share" link for that answer)? – Peter Mortensen Sep 04 '22 at 13:18
You are correct Peter Mortensen! Sorry about that. I updated the answer for more clarification – BJ Rutledge Sep 05 '22 at 18:55

lennoxGER · Answer 15 · 2022-09-06T13:28:37.800

2

Based on the answer from Majbah Habib:

For Windows:

Go to:
Replace in all four files: -g -> --location = global

edited Sep 06 '22 at 13:28

answered Aug 02 '22 at 08:10

lennoxGER

284
1
6

On Windows, presumably? What version and edition was this tested on? [Windows 10 Home](https://en.wikipedia.org/wiki/Windows_10_editions#Baseline_editions)? Please respond by [editing (changing) your answer](https://stackoverflow.com/posts/73204044/edit), not here in comments (******************* ***without*** ************** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Sep 04 '22 at 13:11

Hashim Aziz · Answer 16 · 2023-08-13T23:32:29.063

Download the latest version of Node.js for Windows

As countless other answers have mentioned, this is caused by a bug in a version of Node.js (specifically, a version of NPM that is bundled with Node), but what no other answer seems to have yet mentioned is the simplest way of solving it.

There's no need to edit any files manually or even run anything in the CLI - just grab the latest version of Node.js from the Node.js site.

Let it install and compile what it needs to, and you'll end up with the latest version of Node.js that no longer contains this warning.

Besides that, it's good practice to keep up to date with the latest version of Node.js/NPM you can, and it saves you from needing to update later when Node.js 16 is EOLed on September 11th, 2023.

Yes! I was just about to write the same answer. Please upvote this answer, guys — HoffZ, Mar 03 '23 at 08:41

Samson Royal · Answer 17 · 2023-02-01T02:01:11.747

1

I got a similar error when I installed version 8.12.1 of npm.

Open Command Prompt on Windows or your inbuilt PowerShell terminal in your IDE Visual Studio Code.

Update your current npm version to the latest by using this code in your terminal.

npm i -g npm@latest

It will first display the same error message for something like two lines. Then proceed to install and update; the updated npm version won't display the error message when you run npm -v.

PS: This was tested on a Windows machine running Windows 10 Pro.

edited Feb 01 '23 at 02:01

answered Jul 05 '22 at 13:55

Samson Royal

25
8

Re *"cmd"*: [Implying Windows](https://en.wikipedia.org/wiki/Cmd.exe)? And not using [PowerShell](https://en.wikipedia.org/wiki/PowerShell)? What version and edition of Windows was this tested on? [Windows 10 Home](https://en.wikipedia.org/wiki/Windows_10_editions#Baseline_editions)? Please respond by [editing (changing) your answer](https://stackoverflow.com/posts/72870667/edit), not here in comments (******************* ***without*** ************** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Peter Mortensen Sep 04 '22 at 13:29
This didn't fix the issue for me, error's still there on the next run. – Hashim Aziz Jan 26 '23 at 21:14
Hello @HashimAziz which system are you running this on? what is the nodejs version? – Samson Royal Feb 01 '23 at 01:56

score 1 · Answer 18 · edited Sep 04 '22 at 13:16

1

Just use this code:

npm install --force

edited Sep 04 '22 at 13:16

Peter Mortensen

30,738
21
105
131

answered Jul 17 '22 at 10:41

Mehdi Yaghoubi

561
3
8
24

I am still unable to solve this, tried npm install --force yarn but this doesn't work either – harshikerfuffle Jul 26 '22 at 02:52
update your nodejs and npm – Mehdi Yaghoubi Jul 26 '22 at 18:50

score 1 · Answer 19 · edited Sep 04 '22 at 13:16

1

It's a folder access issue.

Please follow the below steps:

Right-click on the project folder
Click on Property
Uncheck the Read-only checkbox
Click Apply
Then try the npm command again

edited Sep 04 '22 at 13:16

Peter Mortensen

30,738
21
105
131

answered Aug 19 '22 at 09:53

Ganesh Gadekar

39
7

On Windows, presumably? – Peter Mortensen Sep 04 '22 at 13:16

score 0 · Answer 20 · edited Jun 26 '22 at 11:47

It is easy to open and edit the npm.cmd file with Visual Studio Code if you are logged in as administrator.

Right-click the npm.cmd file and choose Open with Code.

The file will open in Visual Studio Code.

Change prefix -g to prefix --location=global

When you are finished and attempt to close the file, Visual Studio Code will have a pop up in the lower right corner with the message:

Failed to save 'npm.cmd': Insufficient permissions. Select 'Retry as Admin' to retry as administrator.

Click 'Retry as Admin'. The npm.cmd file will be saved and the warning no longer appears at start up.

score 0 · Answer 21 · edited Sep 04 '22 at 13:32

0

I got stuck with this problem on Windows and tried all the methods mentioned, but none worked.

This is basically an issue due to the antivirus software. It was considering npm as malware and blocking it. So, I excluded npm from being blocking and it worked.

edited Sep 04 '22 at 13:32

Peter Mortensen

30,738
21
105
131

answered Jul 02 '22 at 08:05

Ritik Banger

2,107
5
25

how did you include npm from being blocked? – harshikerfuffle Jul 26 '22 at 02:54
Reinstall npm and you will get a notification from your antivirus that npm is blocked, click here to unblock. Click on that and it will unblock the same. – Ritik Banger Jul 26 '22 at 04:25
What antivirus software? [Windows Defender](https://en.wikipedia.org/wiki/Microsoft_Defender)? – Peter Mortensen Sep 04 '22 at 13:33
Maybe the defender or any third party application. – Ritik Banger Sep 05 '22 at 04:48

Henke · Answer 22 · 2023-08-14T22:07:47.887

0

A message from the author of the Create React App (CRA):

You absolutely should not be installing react-scripts globally.

The Create React App should be installed locally: npx create-react-app my-app.

Note: in case of issues when uninstalling, see Error while creating a Create React App.

edited Aug 14 '23 at 22:07

answered Mar 29 '23 at 12:25

Henke

4,445
3
31
44

score 0 · Answer 23 · edited Aug 13 '23 at 23:06

0

Delete Node.js and install it again, and the problem will be solved.

edited Aug 13 '23 at 23:06

Peter Mortensen

30,738
21
105
131

answered Apr 01 '23 at 05:48

Hakimeh Mordadi

181
1
16

score -1 · Answer 24 · edited Jun 26 '22 at 11:28

npm WARN config global --global, --local are deprecated. Use --location=global instead. You need to install the following packages:

I am facing the above error, so I simply did these steps:

don't create a folder to write command npx create-react-app project-name on the same drive where you install Node.js
if you install Node.js on the C: drive, then try to make a folder for practicing react on another drive
so I make folder on the D: drive, because I install Node.js on the E: drive
open a command prompt on the folder and then write the command npx create-react-folder my-app

Then your error is solved.

On Windows, presumably? Why would using different drives make any difference? — Peter Mortensen, Jun 26 '22 at 11:34

Message "npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead"

24 Answers24

For Windows users (thanks to Lars) use this library:

Download the latest version of Node.js for Windows

Linked

Related