[DOCS] Unknown configs throw error in npm@12.0.0 release notes - re-open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
- follows on from auto-closed https://github.com/npm/cli/issues/9802
Situation
The release notes for npm@12.0.0 still incorrectly state:
unknown configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.
This statement is incorrect and is not aligned with the updated CHANGELOG 12.0.0 which now states:
unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning. (Unknown .npmrc configs still warn by default; opt into erroring with the new strict-npmrc config.)
Suggestion
Correct also the release notes npm@12.0.0 concerning the description of handling unknown configs in .npmrc.
Note that this is not addressable through a PR. It requires direct write access to the repo in order to edit a release note manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the npm@12.0.0 release page and compare its unknown-config wording with the 12.0.0 entry in CHANGELOG.md. Confirm the release note is the stale text; done means it matches the corrected behavior, including the strict-npmrc detail, though the issue states that direct repository write access is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100