As an npm user, you can create unscoped packages to use in your own projects and publish them to the npm public registry for others to use in theirs. Unscoped packages are always public and are referred to by the package name only:
For more information on package scope, access, and visibility, see “Package scope, access level, and visibility”.
git-remote-urlwith the git remote URL for your package:
git init git remote add origin git://git-remote-url
package.jsonfile. For help naming your package, see “Package name guidelines”.
Publishing sensitive information to the registry can harm your users, compromise your development infrastructure, be expensive to fix, and put you at risk of legal action. We strongly recommend removing sensitive information, such as private keys, passwords, personally identifiable information (PII), and credit card data before publishing your package to the registry.
For less sensitive information, such as testing data, use a
.gitignore file to prevent publishing to the registry. For more information, see this article.
To reduce the chances of publishing bugs, we recommend testing your package before publishing it to the npm registry. To test your package, run
npm install with the full path to your package directory:
npm install my-package
publicbelow the package name on the npm website.
For more information on the
publish command, see the CLI documentation.