dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
@reggi/path-to-regexp
dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2
dependabot/npm_and_yarn/main/eslint-10.4.0
dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0
dependabot/npm_and_yarn/main/proc-log-7.0.0
dependabot/npm_and_yarn/npm_and_yarn-826852524d
dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2
deprecate-totp-2fa
dhei/classic-tokens
gat-bypass-2fa-docs
jpg619/fix-accessibility-content-flow
jpg619/version-bump-tar-2
kartykp/gat-bypass-2fa-docs
kartykp/upgrade-path-to-regex
main
maitxn/version-bump-tar
patch-1
reggi/cache-based-on-version
reggi/dev-engines
reggi/fix-transform-prettier
reggi/overrides
update-search-sensitivity
| 1 | --- |
| 2 | title: About public packages |
| 3 | --- |
| 4 | |
| 5 | As an npm user or organization member, you can create and publish public packages that anyone can download and use in their own projects. |
| 6 | |
| 7 | - **Unscoped** public packages exist in the global public registry namespace and can be referenced in a `package.json` file with the package name alone: `package-name`. |
| 8 | - **Scoped** public packages belong to a user or organization and must be preceded by the user or organization name when included as a dependency in a `package.json` file: |
| 9 | - `@username/package-name` |
| 10 | - `@org-name/package-name` |
| 11 | |
| 12 | ## Next steps |
| 13 | |
| 14 | - "[Creating and publishing scoped public packages][create-scoped-pkg]" |
| 15 | - "[Creating and publishing unscoped public packages][create-unscoped-pkg]" |
| 16 | - "[Using npm packages in your projects][use-pkg]" |
| 17 | |
| 18 | [create-scoped-pkg]: creating-and-publishing-scoped-public-packages |
| 19 | [create-unscoped-pkg]: creating-and-publishing-unscoped-public-packages |
| 20 | [use-pkg]: using-npm-packages-in-your-projects |