fix(config): remove deprecation warning for --global

[darcyclarke]

Summary

A mistake was made creating this issue & subsequently led to us issuing a warning that --global was being removed. For context, --global will be changing it's underlying behaivor to map to --location=global which maps with existing --location-aware commands (ie. npm config & in v9 npm exec)

Exit Criteria

• running npm with --global should not warn users

References & Links

• Release (In-Flight): Release/v8.12.1 cli#4984
• Original intention BREAKING CHANGE(config): map legacy options to --location & --strategy #458
• Mistaken Issue: chore(config): Deprecate & warn for --global (--location=global) #496

[wolfpackt99]

is there a work around?

[mscdex]

@wolfpackt99 Downgrade to npm v8.10.0?

[darcyclarke]

@wolfpackt99 we're shipping a patch right now to remove the deprecation warning as we speak. (ref. npm/cli#4984)

[nlf]

done! published v8.12.1 with this reversed

[alexrosenfeld10]

Is this fixed for sure in 8.12.1?

-- console output produced during zsh initialization follows --

npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
❯ which npm
/Users/alexrosenfeld/.nvm/versions/node/v16.15.1/bin/npm                                                                                                                                                                                            ─╯
❯ npm --version
8.12.1
❯ which node
/Users/alexrosenfeld/.nvm/versions/node/v16.15.1/bin/node
❯ node --version
v16.15.1

[mscdex]

@alexrosenfeld10 Perhaps the npm in your zsh initialization is a different version? Does executing a global command like npm ls -g --depth=0 from your shell prompt print the deprecation warning?

[alexrosenfeld10]

@mscdex yeah, seems like you're right - the initialization must be using a different version, because after initialization that command runs w/o a warning.