Man page - npm-unpublish(1)
Packages contas this manual
- npm-explain(1)
- npm-star(1)
- npm-logout(1)
- npm-arborist(1)
- package-lock-json(5)
- npm-bugs(1)
- npm-shrinkwrap(1)
- npm-dist-tag(1)
- npm-login(1)
- npm-whoami(1)
- npm-doctor(1)
- npm-install(1)
- npm-run-script(1)
- npm-exec(1)
- npm-repo(1)
- npm-docs(1)
- npm-shrinkwrap-json(5)
- npm-edit(1)
- npm-stop(1)
- npm-diff(1)
- npm-find-dupes(1)
- npm-profile(1)
- npm-start(1)
- pacote(1)
- npm-ci(1)
- npm-stars(1)
- npm-update(1)
- npm-ping(1)
- npm-pack(1)
- npm-help-search(1)
- npm-prune(1)
- npm-org(1)
- npmrc(5)
- npm-audit(1)
- npm-unstar(1)
- arborist(1)
- npm-prefix(1)
- npm-publish(1)
- npm-config(1)
- npm-pkg(1)
- npm-adduser(1)
- npm-version(1)
- npm-completion(1)
- npm-install-test(1)
- npm-uninstall(1)
- npm-team(1)
- npm-help(1)
- npm-install-ci-test(1)
- npm-cache(1)
- npm-explore(1)
- npm-link(1)
- npm-root(1)
- package-json(5)
- npm-dedupe(1)
- npm-rebuild(1)
- npm-hook(1)
- npm-ls(1)
- npm-unpublish(1)
- npm-init(1)
- npm-restart(1)
- npm-outdated(1)
- npx(1)
- npm-access(1)
- npm-deprecate(1)
- npm-fund(1)
- npm-query(1)
- npm-owner(1)
- npm-test(1)
- npm-search(1)
- npm-token(1)
- npm-view(1)
- npm(1)
- node-npmcli-package-json
- node-libnpmpublish
- node-libnpmhook
- node-npm-packlist
- node-npmcli-installed-package-contents
- node-libnpmorg
- node-libnpmsearch
- node-npmcli-arborist
- node-npmcli-metavuln-calculator
- node-npmcli-mock-registry
- node-npmcli-disparity-colors
- node-npmcli-config
- node-pacote
- node-libnpmpack
- node-npmcli-map-workspaces
- node-libnpmaccess
- npm
- node-npmcli-smoke-tests
- node-libnpmversion
- node-npmcli-query
- node-libnpmteam
- node-npmcli-name-from-folder
- node-libnpmfund
- node-npmcli-promise-spawn
- node-libnpmdiff
- node-npmcli-run-script
- node-qrcode-terminal
- node-npmcli-node-gyp
- node-npmcli-git
- node-libnpmexec
apt-get install npm
Manual
| NPM-UNPUBLISH(1) | General Commands Manual | NPM-UNPUBLISH(1) |
NAME
npm-unpublish
Synopsis
<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
To learn more about how the npm registry treats unpublish, see our <a href="https://docs.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a>
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.
Description
This removes a package version from the registry, deleting its
entry and
removing the tarball.
The npm registry will return an error if you are not logged
in.
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.
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.
Configuration
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
See Also
- package spec
- npm deprecate
- npm publish
- npm registry
- npm adduser
- npm owner
- npm login
| May 2024 | 9.2.0 |