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.

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

[RRFC] npm deprecate multiple packages #341

Open
ruyadorno opened this issue Mar 15, 2021 · 1 comment
Open

[RRFC] npm deprecate multiple packages #341

ruyadorno opened this issue Mar 15, 2021 · 1 comment

Comments

@ruyadorno
Copy link
Contributor

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

@ljharb
Copy link
Contributor

ljharb commented Mar 15, 2021

npm deprecate is a potentially destructive command, so it seems safer not to support it with no args, but using explicit specifiers seems fine, and with explicit workspaces.

It's probably safer to not implicitly deprecate an entire repo when no args are provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants