You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
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.
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
The text was updated successfully, but these errors were encountered: