[RRFC] npm deprecate multiple packages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 777
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
Motivation ("The Why")
Currently npm deprecate can only handle one package at a time, and only through a <pkg>@<version> syntax. Given the work towards providing better workspaces workflows, it's very likely going to be an important feature tu support with more folks managing multiple packages from a single place.
Example
Some possible alternative syntaxes we might to consider supporting:
npm deprecate (no args? deprecates the current version of the current package?)
npm deprecate foo@1.0.0 bar@1.2.3 baz@2.0.0
npm deprecate --workspaces (same as no args but for all workspace packages?)
References
- Spawned by the discussions during the workspaces implementation over at the cli repo: https://github.com/npm/cli/pull/2836#discussion_r589092316
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 by reading the proposed npm deprecate syntaxes and the linked npm/cli discussion, especially the workspace context. No files or tests are named; done would require an agreed proposal defining multi-package and workspace behavior through the RFC process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100