File Explorer

1.TH "NPM-UNPUBLISH" "1" "February 2026" "NPM@11.11.0" ""2.SH "NAME"3\fBnpm-unpublish\fR - Remove a package from the registry4.SS "Synopsis"5.P6.RS 27.nf8npm unpublish \[lB]<package-spec>\[rB]9.fi10.RE11.P12To learn more about how the npm registry treats unpublish, see our \fBunpublish policies\fR \fI\(lahttps://docs.npmjs.com/policies/unpublish\(ra\fR.13.SS "Warning"14.P15Consider using the npm help deprecate command instead, if your intent is to encourage users to upgrade, or if you no longer want to maintain a package.16.SS "Description"17.P18This removes a package version from the registry, deleting its entry and removing the tarball.19.P20The npm registry will return an error if you are not npm help "logged in".21.P22If you do not specify a package name at all, the name and version to be unpublished will be pulled from the project in the current directory.23.P24If you specify a package name but 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.25.P26Even 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.27.SS "Configuration"28.SS "\fBdry-run\fR"29.RS 030.IP \(bu 431Default: false32.IP \(bu 433Type: Boolean34.RE 035 36.P37Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, \fBinstall\fR, \fBupdate\fR, \fBdedupe\fR, \fBuninstall\fR, as well as \fBpack\fR and \fBpublish\fR.38.P39Note: This is NOT honored by other network related commands, eg \fBdist-tags\fR, \fBowner\fR, etc.40.SS "\fBforce\fR"41.RS 042.IP \(bu 443Default: false44.IP \(bu 445Type: Boolean46.RE 047 48.P49Removes various protections against unfortunate side effects, common mistakes, unnecessary performance degradation, and malicious input.50.RS 051.IP \(bu 452Allow clobbering non-npm files in global installs.53.IP \(bu 454Allow the \fBnpm version\fR command to work on an unclean git repository.55.IP \(bu 456Allow deleting the cache folder with \fBnpm cache clean\fR.57.IP \(bu 458Allow installing packages that have an \fBengines\fR declaration requiring a different version of npm.59.IP \(bu 460Allow installing packages that have an \fBengines\fR declaration requiring a different version of \fBnode\fR, even if \fB--engine-strict\fR is enabled.61.IP \(bu 462Allow \fBnpm audit fix\fR to install modules outside your stated dependency range (including SemVer-major changes).63.IP \(bu 464Allow unpublishing all versions of a published package.65.IP \(bu 466Allow conflicting peerDependencies to be installed in the root project.67.IP \(bu 468Implicitly set \fB--yes\fR during \fBnpm init\fR.69.IP \(bu 470Allow clobbering existing values in \fBnpm pkg\fR71.IP \(bu 472Allow unpublishing of entire packages (not just a single version).73.RE 074 75.P76If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!77.SS "\fBworkspace\fR"78.RS 079.IP \(bu 480Default:81.IP \(bu 482Type: String (can be set multiple times)83.RE 084 85.P86Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option.87.P88Valid values for the \fBworkspace\fR config are either:89.RS 090.IP \(bu 491Workspace names92.IP \(bu 493Path to a workspace directory94.IP \(bu 495Path to a parent workspace directory (will result in selecting all workspaces within that folder)96.RE 097 98.P99When set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.100.P101This value is not exported to the environment for child processes.102.SS "\fBworkspaces\fR"103.RS 0104.IP \(bu 4105Default: null106.IP \(bu 4107Type: null or Boolean108.RE 0109 110.P111Set to true to run the command in the context of \fBall\fR configured workspaces.112.P113Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:114.RS 0115.IP \(bu 4116Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config.117.RE 0118 119.P120This value is not exported to the environment for child processes.121.SS "See Also"122.RS 0123.IP \(bu 4124npm help "package spec"125.IP \(bu 4126npm help deprecate127.IP \(bu 4128npm help publish129.IP \(bu 4130npm help registry131.IP \(bu 4132npm help adduser133.IP \(bu 4134npm help owner135.IP \(bu 4136npm help login137.RE 0138