Packages and modules
Contributing packages to the registry
Creating a package.json fileCreating Node.js modulesAbout package README filesCreating and publishing unscoped public packagesCreating and publishing scoped public packagesCreating and publishing private packagesPackage name guidelinesSpecifying dependencies and devDependencies in a package.json fileAbout semantic versioningAdding dist-tags to packages
Package name guidelines
When choosing a name for your package, choose a name that
- is unique
- is descriptive
- meets npm policy guidelines. For example, do not give your package an offensive name, and do not use someone else's trademarked name or violate the npm trademark policy.
Additionally, when choosing a name for an unscoped package, also choose a name that
- is not already owned by someone else
- is not spelled in a similar way to another package name
- will not confuse others about authorship