Publish a package
npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] Publishes '.' if no argument supplied Sets tag 'latest' if no --tag specified
Publishes a package to the registry so that it can be installed by name. All
files in the package directory are included if no local
.npmignore file exists. If both files exist and a file is ignored by
.gitignore but not by
.npmignore then it will be included. See
npm-developers(7) for full details on what's included in the published
package, as well as details on how the package is built.
A folder containing a package.json file
A url or file path to a gzipped tar archive containing a single folder
with a package.json file inside.
Registers the published package with the given tag, such that
<name>@<tag> will install this version. By default,
npm publish updates
npm install installs the
latest tag. See
details about tags.
Tells the registry whether this package should be published as public or
restricted. Only applies to scoped packages, which default to
If you don't have a paid account, you must publish with
to publish scoped packages.
Fails if the package name and version combination already exists in the specified registry.
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-unpublish(1).
npm@5, both a sha1sum and an integrity field with a sha512sum of the
tarball will be submitted to the registry during publication. Subsequent
installs will use the strongest supported algorithm to verify downloads.
For a "dry run" that does everything except actually publishing to the
npm-pack(1), which figures out the files to be included and
packs them into a tarball to be uploaded to the registry.