from small one page howto to huge articles all in one place
 

search text in:





Poll
What does your sytem tell when running "ulimit -u"?








poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

122331

userrating:

average rating: 1.7 (86 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

234062

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

114284

userrating:

average rating: 1.3 (28 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





NPM\-PUBLISH

Section: (1)
Updated: December 2016
Index Return to Main Contents
 

NAME

npm-publish - Publish a package  

SYNOPSIS

npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>]

Publishes '.' if no argument supplied
Sets tag 'latest' if no --tag specified
 

DESCRIPTION

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 .gitignore or .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 help 7 npm-developers for full details on what's included in the published package, as well as details on how the package is built. 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 npm-scope in the name (see npm help 5 package.json).
*
<folder>: A folder containing a package.json file
*
<tarball>: A url or file path to a gzipped tar archive containing a single folder with a package.json file inside.
*
[--tag <tag>] Registers the published package with the given tag, such that npm install <name>@<tag> will install this version. By default, npm publish updates and npm install installs the latest tag. See npm help npm-dist-tag for details about tags.
*
[--access <public|restricted>] Tells the registry whether this package should be published as public or restricted. Only applies to scoped packages, which default to restricted. If you don't have a paid account, you must publish with --access public 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 help unpublish. For a "dry run" that does everything except actually publishing to the registry, see npm help npm-pack, which figures out the files to be included and packs them into a tarball to be uploaded to the registry.  

SEE ALSO

*
npm help 7 registry
*
npm help 7 scope
*
npm help adduser
*
npm help owner
*
npm help deprecate
*
npm help dist-tag
*
npm help pack


 

Index

NAME
SYNOPSIS
DESCRIPTION
SEE ALSO





Other free services
toURL.org
Shorten long
URLs to short
links like
http://tourl.org/2
tourl.org
.
Reverse DNS lookup
Find out which hostname(s)
resolve to a
given IP or other hostnames for the server
www.reversednslookup.org
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2018 Sascha Nitsch Unternehmensberatung UG(haftungsbeschränkt)
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 3.2 ms