node/deps/npm/man/man1/npm-publish.1

.TH "NPM\-PUBLISH" "1" "February 2015" "" ""
.SH "NAME"
\fBnpm-publish\fR \- Publish a package
.SH SYNOPSIS
.P
.RS 2
.nf
npm publish <tarball> [\-\-tag <tag>] [\-\-access <public|restricted>]
npm publish <folder> [\-\-tag <tag>] [\-\-access <public|restricted>]
.fi
.RE
.SH DESCRIPTION
.P
Publishes a package to the registry so that it can be installed by name\. See
npm help 7 \fBnpm\-developers\fR for details on what's included in the published package, as
well as details on how the package is built\.
.P
By default npm will publish to the public registry\. This can be overridden by
specifying a different default registry or using a npm help 7 \fBnpm\-scope\fR in the name
(see npm help 5 \fBpackage\.json\fR)\.
.RS 0
.IP \(bu 2
\fB<folder>\fR:
A folder containing a package\.json file
.IP \(bu 2
\fB<tarball>\fR:
A url or file path to a gzipped tar archive containing a single folder
with a package\.json file inside\.
.IP \(bu 2
\fB[\-\-tag <tag>]\fR
Registers the published package with the given tag, such that \fBnpm install
<name>@<tag>\fR will install this version\.  By default, \fBnpm publish\fR updates
and \fBnpm install\fR installs the \fBlatest\fR tag\.
.IP \(bu 2
\fB[\-\-access <public|restricted>]\fR
Tells the registry whether this package should be published as public or
restricted\. Only applies to scoped packages, which default to \fBrestricted\fR\|\.
If you don't have a paid account, you must publish with \fB\-\-access public\fR
to publish scoped packages\.

.RE
.P
Fails if the package name and version combination already exists in
the specified registry\.
.P
Once a package is published with a given name and version, that
specific name and version combination can never be used again, even if
it is removed with npm help unpublish\.
.SH SEE ALSO
.RS 0
.IP \(bu 2
npm help 7 registry
.IP \(bu 2
npm help 7 scope
.IP \(bu 2
npm help adduser
.IP \(bu 2
npm help owner
.IP \(bu 2
npm help deprecate
.IP \(bu 2
npm help tag

.RE