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

fix(docs): clean up npm unpublish docs #2474

Closed
wants to merge 2 commits into from
Closed

fix(docs): clean up npm unpublish docs #2474

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
10099b3
fix(docs): clean up `npm unpublish` docs
wraithgar Jan 11, 2021
79b2c91
fix(docs): move unpublish policy to top
wraithgar Jan 14, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
27 changes: 18 additions & 9 deletions docs/content/commands/npm-unpublish.md
View file
Open in desktop
Expand Up @@ -20,22 +20,30 @@ npm unpublish [<@scope>/]<pkg> --force

### Warning

Consider using the `deprecate` command instead, if your intent is to encourage users to upgrade, or if you no longer want to maintain a package.
Consider using the [deprecate](/commands/npm-deprecate) command instead,
wraithgar marked this conversation as resolved.
Show resolved Hide resolved
if your intent is to encourage users to upgrade, or if you no longer
want to maintain a package.

### Description

This removes a package version from the registry, deleting its
entry and removing the tarball.
This removes a package version from the registry, deleting its entry and
removing the tarball.

If no version is specified, or if all versions are removed then
the root package entry is removed from the registry entirely.
The npm registry will return an error if you are not [logged
in](/commands/npm-login).

Even if a package version is unpublished, that specific name and
version combination can never be reused. In order to publish the
package again, a new version number must be used. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.
If you do not specify a version or if you remove all of a package's
versions then the registry will remove the root package entry entirely.

To learn more about how unpublish is treated on the npm registry, see our <a href="https://www.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>.
Even if you unpublish a package version, that specific name and version
combination can never be reused. In order to publish the package again,
you must use a new version number. If you unpublish the entire package,
you may not publish any new versions of that package until 24 hours have
passed.

To learn more about how the npm registry treats unpublish, see our <a
wraithgar marked this conversation as resolved.
Show resolved Hide resolved
href="https://www.npmjs.com/policies/unpublish" target="_blank"
rel="noopener noreferrer"> unpublish policies</a>

### See Also

Expand All @@ -44,3 +52,4 @@ To learn more about how unpublish is treated on the npm registry, see our <a hre
* [npm registry](/using-npm/registry)
* [npm adduser](/commands/npm-adduser)
* [npm owner](/commands/npm-owner)
* [npm login](/commands/npm-login)
2 changes: 1 addition & 1 deletion lib/unpublish.js
View file
Open in desktop
Expand Up @@ -35,7 +35,7 @@ const completionFn = async (args) => {
const access = await libaccess.lsPackages(username, opts)
// do a bit of filtering at this point, so that we don't need
// to fetch versions for more than one thing, but also don't
// accidentally a whole project
// accidentally unpublish a whole project
let pkgs = Object.keys(access || {})
if (!partialWord || !pkgs.length)
return pkgs
Expand Down