about | npm Documentation

npm is lots of things.

npm is the package manager for Node.js. It was created in 2009 as an open source project to help JavaScript developers easily share packaged modules of code.

The npm Registry is a public collection of packages of open-source code for Node.js, front-end web apps, mobile apps, robots, routers, and countless other needs of the JavaScript community.

npm is the command line client that allows developers to install and publish those packages.

npm, Inc. is the company that hosts and maintains all of the above.

About npm, Inc.

npm, Inc. is a company co-founded in 2014 by npm's creator, Isaac Z. Schlueter, along with Laurie Voss and Rod Boothby.

npm, Inc. is dedicated to the long term success of the JavaScript community, which includes the success of the open-source Node.js and npm projects.

At npm, Inc. we do three things to support this goal:

Run the open source registry as a free service.

Build tools and operate services that support the secure use of packages in a private or enterprise context.

Build innovative new tools and services for the developer community.

npm's mission is to take Open Source development to entirely new places. When everyone else is adding force, we work to reduce friction.

npm is not a typical product, and we are not a typical "work hard/play hard" startup. We are responsible adults with diverse backgrounds and interests, who take our careers and our lives seriously. We believe that the best way to iterate towards success is by taking care of ourselves, our families, our users, and one another. We aim for a sustainable approach to work and life, because that is the best way to maximize long-term speed, while retaining clarity of vision. Compassion is our strategy.

Our offices are in downtown Oakland, California.

Getting Started

How npm works

Private Modules

Organizations

Using npm

coding-style npm's "funny" coding style
config More than you probably want to know about npm configuration
developers Developer Guide
disputes Handling Module Name Disputes
orgs Working with Teams & Orgs
registry The JavaScript Package Registry
removing-npm Cleaning the Slate
scope Scoped packages
scripts How npm handles the "scripts" field
semver The semantic versioner for npm

npm On-Site

CLI Commands

access Set access level on published packages
adduser Add a registry user account
bin Display npm bin folder
bugs Bugs for a package in a web browser maybe
build Build a package
bundle REMOVED
cache Manipulates packages cache
completion Tab Completion for npm
config Manage the npm configuration files
dedupe Reduce duplication
deprecate Deprecate a version of a package
dist-tag Modify package distribution tags
docs Docs for a package in a web browser maybe
edit Edit an installed package
explore Browse an installed package
help Get help on npm
help-search Search npm help documentation
init Interactively create a package.json file
install Install a package
install-test
link Symlink a package folder
logout Log out of the registry
ls List installed packages
npm javascript package manager
outdated Check for outdated packages
owner Manage package owners
pack Create a tarball from a package
ping Ping npm registry
prefix Display prefix
prune Remove extraneous packages
publish Publish a package
rebuild Rebuild a package
repo Open package repository page in the browser
restart Restart a package
root Display npm root
run-script Run arbitrary package scripts
search Search for packages
shrinkwrap Lock down dependency versions
star Mark your favorite packages
stars View packages marked as favorites
start Start a package
stop Stop a package
tag Tag a published version
team Manage organization teams and team memberships
test Test a package
uninstall Remove a package
unpublish Remove a package from the registry
update Update a package
version Bump a package version
view View registry info
whoami Display npm username

Configuring npm

folders Folder Structures Used by npm
npmrc The npm config files
package.json Specifics of npm's package.json handling

About npm