Skip to content
npm Docs
npmjs.comStatusSupport
About npm
Getting started
Packages and modules
Integrations
Organizations
npm Enterprise
npm CLI
CLI Commands
npmnpm accessnpm addusernpm auditnpm binnpm bugsnpm cachenpm cinpm completionnpm confignpm dedupenpm deprecatenpm diffnpm dist-tagnpm docsnpm doctornpm editnpm execnpm explainnpm explorenpm find-dupesnpm fundnpm helpnpm help-searchnpm hooknpm initnpm installnpm install-ci-testnpm install-testnpm linknpm logoutnpm lsnpm orgnpm outdatednpm ownernpm packnpm pingnpm prefixnpm profilenpm prunenpm publishnpm rebuildnpm reponpm restartnpm rootnpm run-scriptnpm searchnpm set-scriptnpm shrinkwrapnpm starnpm starsnpm startnpm stopnpm teamnpm testnpm tokennpm uninstallnpm unpublishnpm unstarnpm updatenpm versionnpm viewnpm whoaminpx
Configuring npm
Using npm

npm-unpublish

Remove a package from the registry
Version 7.x (Current release)
  • Version 6.x (Legacy release)
  • Version 7.x (Current release)
Table of contents
Table of contents

Synopsis

To learn more about how the npm registry treats unpublish, see our unpublish policies

Unpublishing a single version of a package

npm unpublish [<@scope>/]<pkg>@<version>

Unpublishing an entire package

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.

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.

See Also