Nodejitsu has joined GoDaddyWe are excited to join GoDaddy to help spearhead their largest Node.js product: Website Builder. As a part of this Nodejitsu will help existing customers transition onto new solutions for their hosting needs until early August 2015. Please migrate your applications from the Nodejitsu platform before the end of the transition period. Please read our blog post to learn more about customer transition plans and our continued support for Open Source within the node community.
Most of the workflow of npm is being done in the command line, we will show you the basic commands you'll need to know to work with Private npm from the CLI.
First we need to setup our npm client to use your Private npm registry, with the following commands your local npm client will be ready to work with Private npm.
$ npm config set always-auth true $ npm config set strict-ssl true $ npm config set ca "" $ npm config set registry https://<your-subdomain>.registry.nodejitsu.com
After setting this options you'll need to login by running:
$ npm login
This will sync your Public npm user with our Private npm product.
Next we will learn how to use npm for common package management.
If you want to install a package from your private or public registry you'll want to run:
$ npm install <package-name>
Also if you want to save the package dependency in your package.json file just append the
--save option to the command.
$ npm install <package-name> --save
Or if the package is a development dependency (like grunt, karma, etc.) you'll want to append
$ npm install <package-name> --save-dev
Publish a package is so easy with npm, just run the following command to publish a package to your private registry (make sure you followed the setup steps properly).
$ npm publish
But if you want to publish the package to the public registry you can use the
--reg option to define the npm registry to use.
$ npm publish --reg https://registry.npmjs.org
If you want to unpublish a package you'll want to run:
$ npm unpublish <package-name> --force
Take into account that if you want to publish the package again you'll need to use a different version name in your package.json to avoid conflicts.
Work in a team is awesome right? With npm, team management is easy too!
If you want to know the maintaners of a package run:
$ npm owner ls <package-name>
If you want to add a maintainer you'll need to run:
$ npm owner add <username> <package-name>
And if you want to remove a maintainer, run:
$ npm owner rm <username> <package-name>
Protip: After adding or removing a maintainer don't forget to Sync it on the Web Interface using
Sync Maintainers button.
Learn how to set up Nodejitsu's tool for app deployment and be ready for action.