Consider 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.
If 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.
.P
If 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.
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.
Indicates 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.
Allow clobbering non-npm files in global installs.
.IP\(bu4
Allow the \fBnpm version\fR command to work on an unclean git repository.
.IP\(bu4
Allow deleting the cache folder with \fBnpm cache clean\fR.
.IP\(bu4
Allow installing packages that have an \fBengines\fR declaration requiring a different version of npm.
.IP\(bu4
Allow installing packages that have an \fBengines\fR declaration requiring a different version of \fBnode\fR, even if \fB--engine-strict\fR is enabled.
.IP\(bu4
Allow \fBnpm audit fix\fR to install modules outside your stated dependency range (including SemVer-major changes).
.IP\(bu4
Allow unpublishing all versions of a published package.
.IP\(bu4
Allow conflicting peerDependencies to be installed in the root project.
.IP\(bu4
Implicitly set \fB--yes\fR during \fBnpm init\fR.
.IP\(bu4
Allow clobbering existing values in \fBnpm pkg\fR
.IP\(bu4
Allow unpublishing of entire packages (not just a single version).
Enable 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.
When 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.
Commands 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.
