Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BREAKING CHANGE(config): npm 9 should refuse to set deprecated config items. #535

Closed
Tracked by #443
wraithgar opened this issue Aug 15, 2022 · 1 comment
Closed
Tracked by #443

BREAKING CHANGE(config): npm 9 should refuse to set deprecated config items. #535

wraithgar opened this issue Aug 15, 2022 · 1 comment
Assignees
@wraithgar
Labels
feature
Milestone
v9.0.0

Comments

@wraithgar
Copy link
Member

Our deprecation warnings show items as flags, which means if you npm config set foo where foo is deprecated you get a warning that implies you used --foo. We can't really change our deprecation warnings because then folks would inevitably complain that foo is an invalid param (without the --).

A simple solution is to stop allowing npm config itself setting deprecated configs.
@wraithgar wraithgar mentioned this issue Aug 15, 2022
Closed
2 tasks
@lukekarrys lukekarrys changed the title [Breaking] npm 9 should refuse to set deprecated config items. BREAKING CHANGE(config): npm 9 should refuse to set deprecated config items. Sep 2, 2022
@lukekarrys lukekarrys mentioned this issue Sep 2, 2022
Closed
32 tasks
@lukekarrys lukekarrys added this to the v9.0.0 milestone Sep 2, 2022
@wraithgar wraithgar mentioned this issue Oct 19, 2022
Merged
@Taishawnk
Copy link

What is the fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wraithgar wraithgar

Labels
feature
Projects
None yet
Milestone
v9.0.0
Development

No branches or pull requests
4 participants
@wraithgar @darcyclarke @lukekarrys @Taishawnk