When managing your package.json file there are 2 use cases that can impact how you configure it:
I don't want my package published at all. It's private.
To enable this set "private": true
in your package.json. This will prevent it from being published at all.
If you try to accidently publish the package, you’ll get the following feedback:
C:\projects\test\npmtest>npm publish
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\BaWu\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "publish"
npm ERR! node v6.10.0
npm ERR! npm v3.10.5npm ERR! This package has been marked as private
npm ERR! Remove the 'private' field from the package.json to publish it.
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>npm ERR! Please include the following file with any support request:
npm ERR! C:\projects\test\npmtest\npm-debug.log
I only want my package to be published to an internal registry.
Add a "publishConfig":{"registry":"http://my-internal-registry.local"}
section to your package.json to force it to be published only to your internal registry.
Invoking the ‘npm publish’ command will publish the package to the specified registry.
More information at http://browsenpm.org/package.json