Private modules are ordinary npm packages that only you, and people you select, can view, install, and publish. You publish them in your namespace or your team's namespace, just by giving them a name in package.json:
You publish them with npm publish, just like any other package, and you install
them by name:
npm install @myuser/mypackage
Once installed, use them by requiring them by name, just like any package:
var mypackage = require'@myuser/mypackage';
You re-use code between projects. npm and the registry make it really easy to share small modules of useful code with the world. But sometimes the code in that package is private, or sensitive, or just too specific to your needs for you to want to publish it to the public registry. Private packages are great for this.
You work in a team, or you work for clients. You want to be able to easily share your work, with the dependency management and version management that npm provides. By making it easy and granular to select who can see, install and publish packages, private packages make this easy.
Last modified December 29, 2015 Found a typo? Send a pull request!