fix: undeprecate and remove warnings for --global, -g, --local

[fritzy]

Internally, we made a mistake in deprecating --global, and are correcting that with this PR.

The original PR is here. #4879

This removes deprecation warnings and updates documentation.

[npm-cli-bot]

no statistically significant performance changes detected

timing results

app-large	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	34.652 ±0.36	17.226 ±0.01	15.835 ±0.26	18.100 ±0.76	2.755 ±0.01	2.706 ±0.00	2.199 ±0.00	10.677 ±0.01	2.187 ±0.02	3.516 ±0.47
#4982	35.993 ±1.23	17.275 ±0.01	15.750 ±0.02	18.603 ±0.86	2.776 ±0.00	2.741 ±0.04	2.266 ±0.06	10.866 ±0.09	2.153 ±0.00	3.373 ±0.24

app-medium	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	25.460 ±1.57	12.999 ±0.28	11.564 ±0.02	12.239 ±0.14	2.515 ±0.04	2.524 ±0.01	2.224 ±0.05	7.917 ±0.11	2.078 ±0.01	2.850 ±0.03
#4982	25.588 ±0.80	12.940 ±0.02	11.417 ±0.07	12.581 ±0.02	2.490 ±0.03	2.463 ±0.00	2.225 ±0.07	7.884 ±0.11	2.118 ±0.04	2.776 ±0.02

[nickmccurdy]

I'm still getting the following error on 18.12.1. Is there a regression?

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

[U-C-S]

Same, Still having it after updating with npm i -g npm@latest

EDIT:
nodejs/node#43323 (comment)

[yemymy]

I am using the latest version and seeing this problem --global

[hlp2020]

How to save this problem?

[bennycode]

Seems to be fine with v8.13.1. There are YouTubers advising to manually modify npm and npm.cmd which I don't think is advisable (https://www.youtube.com/watch?v=ySh16mC7Zws). Will report that to them.

[nuhaaM]

I still have that issue on the latest version v8.13.2

[bennycode]

I still have that issue on the latest version v8.13.2

In that case you can try this workaround 🙈: https://youtu.be/7xEgFfpUeEs?t=232

[ruyadorno]

Seems to be fine with v8.13.1. There are YouTubers advising to manually modify npm and npm.cmd which I don't think is advisable (https://www.youtube.com/watch?v=ySh16mC7Zws). Will report that to them.

right, that sounds like whoever is still seeing this error message is getting it from the binary jumper thing that retrieves the global prefix in order to enable npm to use a diff (oftentimes updated) version of itself, ref:

cli/bin/npm

Line 23 in ef8d2ed

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

A possible clean solution would be to uninstall node + npm (however you got it) and install it again.

[mrauhu]

Right now this pull request is merged but not released.

@fritzy can you please bump the npm package version?

[awxiaoxian2020]

Right now this pull request is merged but not released.

@fritzy can you please bump the npm package version?

Any Response?