FM / man1

/usr/local/lib/node_modules/npm/man/man1/

/usr/local/lib/node_modules/npm/man/man1

Name	Size	Mode	Actions
npm-access.1	3270	0644	edit dl rm
npm-adduser.1	2207	0644	edit dl rm
npm-audit.1	18066	0644	edit dl rm
npm-bugs.1	3390	0644	edit dl rm
npm-cache.1	3695	0644	edit dl rm
npm-ci.1	10884	0644	edit dl rm
npm-completion.1	999	0644	edit dl rm
npm-config.1	4646	0644	edit dl rm
npm-dedupe.1	10565	0644	edit dl rm
npm-deprecate.1	2379	0644	edit dl rm
npm-diff.1	9781	0644	edit dl rm
npm-dist-tag.1	5646	0644	edit dl rm
npm-docs.1	3372	0644	edit dl rm
npm-doctor.1	5374	0644	edit dl rm
npm-edit.1	1190	0644	edit dl rm
npm-exec.1	12510	0644	edit dl rm
npm-explain.1	2939	0644	edit dl rm
npm-explore.1	1091	0644	edit dl rm
npm-find-dupes.1	7586	0644	edit dl rm
npm-fund.1	4073	0644	edit dl rm
npm-get.1	546	0644	edit dl rm
npm-help-search.1	869	0644	edit dl rm
npm-help.1	1101	0644	edit dl rm
npm-init.1	11590	0644	edit dl rm
npm-install-ci-test.1	9023	0644	edit dl rm
npm-install-test.1	13086	0644	edit dl rm
npm-install.1	31718	0644	edit dl rm
npm-link.1	13653	0644	edit dl rm
npm-ll.1	6591	0644	edit dl rm
npm-login.1	2558	0644	edit dl rm
npm-logout.1	1889	0644	edit dl rm
npm-ls.1	7964	0644	edit dl rm
npm-org.1	2312	0644	edit dl rm
npm-outdated.1	7759	0644	edit dl rm
npm-owner.1	3365	0644	edit dl rm
npm-pack.1	4326	0644	edit dl rm
npm-ping.1	851	0644	edit dl rm
npm-pkg.1	8722	0644	edit dl rm
npm-prefix.1	1306	0644	edit dl rm
npm-profile.1	3423	0644	edit dl rm
npm-prune.1	6453	0644	edit dl rm
npm-publish.1	8842	0644	edit dl rm
npm-query.1	7688	0644	edit dl rm
npm-rebuild.1	5659	0644	edit dl rm
npm-repo.1	3154	0644	edit dl rm
npm-restart.1	1690	0644	edit dl rm
npm-root.1	1196	0644	edit dl rm
npm-run.1	8383	0644	edit dl rm
npm-sbom.1	8999	0644	edit dl rm
npm-search.1	4067	0644	edit dl rm
npm-set.1	1632	0644	edit dl rm
npm-shrinkwrap.1	999	0644	edit dl rm
npm-star.1	1809	0644	edit dl rm
npm-stars.1	797	0644	edit dl rm
npm-start.1	1824	0644	edit dl rm
npm-stop.1	1454	0644	edit dl rm
npm-team.1	4505	0644	edit dl rm
npm-test.1	1367	0644	edit dl rm
npm-token.1	5522	0644	edit dl rm
npm-trust.1	10532	0644	edit dl rm
npm-undeprecate.1	1579	0644	edit dl rm
npm-uninstall.1	4988	0644	edit dl rm
npm-unpublish.1	4902	0644	edit dl rm
npm-unstar.1	1660	0644	edit dl rm
npm-update.1	14461	0644	edit dl rm
npm-version.1	9064	0644	edit dl rm
npm-view.1	8076	0644	edit dl rm
npm-whoami.1	875	0644	edit dl rm
npm.1	5968	0644	edit dl rm
npx.1	6865	0644	edit dl rm

Edit: /usr/local/lib/node_modules/npm/man/man1/npm-unpublish.1 (4902B)

.TH "NPM-UNPUBLISH" "1" "March 2026" "NPM@11.12.0" ""
.SH "NAME"
\fBnpm-unpublish\fR - Remove a package from the registry
.SS "Synopsis"
.P
.RS 2
.nf
npm unpublish \[lB]<package-spec>\[rB]
.fi
.RE
.P
To learn more about how the npm registry treats unpublish, see our \fBunpublish policies\fR \fI\(lahttps://docs.npmjs.com/policies/unpublish\(ra\fR.
.SS "Warning"
.P
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.
.SS "Description"
.P
This removes a package version from the registry, deleting its entry and removing the tarball.
.P
The npm registry will return an error if you are not npm help "logged in".
.P
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.
.P
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.
.SS "Configuration"
.SS "\fBdry-run\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
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.
.P
Note: This is NOT honored by other network related commands, eg \fBdist-tags\fR, \fBowner\fR, etc.
.SS "\fBforce\fR"
.RS 0
.IP \(bu 4
Default: false
.IP \(bu 4
Type: Boolean
.RE 0

.P
Removes various protections against unfortunate side effects, common mistakes, unnecessary performance degradation, and malicious input.
.RS 0
.IP \(bu 4
Allow clobbering non-npm files in global installs.
.IP \(bu 4
Allow the \fBnpm version\fR command to work on an unclean git repository.
.IP \(bu 4
Allow deleting the cache folder with \fBnpm cache clean\fR.
.IP \(bu 4
Allow installing packages that have an \fBengines\fR declaration requiring a different version of npm.
.IP \(bu 4
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 \(bu 4
Allow \fBnpm audit fix\fR to install modules outside your stated dependency range (including SemVer-major changes).
.IP \(bu 4
Allow unpublishing all versions of a published package.
.IP \(bu 4
Allow conflicting peerDependencies to be installed in the root project.
.IP \(bu 4
Implicitly set \fB--yes\fR during \fBnpm init\fR.
.IP \(bu 4
Allow clobbering existing values in \fBnpm pkg\fR
.IP \(bu 4
Allow unpublishing of entire packages (not just a single version).
.RE 0

.P
If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!
.SS "\fBworkspace\fR"
.RS 0
.IP \(bu 4
Default:
.IP \(bu 4
Type: String (can be set multiple times)
.RE 0

.P
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.
.P
Valid values for the \fBworkspace\fR config are either:
.RS 0
.IP \(bu 4
Workspace names
.IP \(bu 4
Path to a workspace directory
.IP \(bu 4
Path to a parent workspace directory (will result in selecting all workspaces within that folder)
.RE 0

.P
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.
.P
This value is not exported to the environment for child processes.
.SS "\fBworkspaces\fR"
.RS 0
.IP \(bu 4
Default: null
.IP \(bu 4
Type: null or Boolean
.RE 0

.P
Set to true to run the command in the context of \fBall\fR configured workspaces.
.P
Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:
.RS 0
.IP \(bu 4
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.
.RE 0

.P
This value is not exported to the environment for child processes.
.SS "See Also"
.RS 0
.IP \(bu 4
npm help "package spec"
.IP \(bu 4
npm help deprecate
.IP \(bu 4
npm help publish
.IP \(bu 4
npm help registry
.IP \(bu 4
npm help adduser
.IP \(bu 4
npm help owner
.IP \(bu 4
npm help login
.RE 0

cmd: