npm/pnpm/yarn

Publish Commands

Publish packages to the npm registry. Learn version management, scoped packages, access control, and best practices for maintaining public and private packages.

9 commands

Pro Tips

Use 'npm pack --dry-run' to see exactly which files will be included in your published package.

Use 'npm version patch|minor|major' to bump version, create a git tag, and update package.json in one command.

Add 'files' field in package.json to whitelist published files — more reliable than .npmignore.

Common Mistakes

Published packages cannot be fully deleted after 72 hours — only unpublished. Double-check before publishing.

Accidentally publishing private code is a common mistake. Use 'private: true' in package.json for non-publishable packages.

Commands

Publish package

$ npm publish

Publish package to registry.

Publish public scoped

$ npm publish --access public

Publish scoped package as public.

Publish with tag

$ npm publish --tag beta

Publish with specific tag (beta, next, etc.).

Create tarball

$ npm pack

Create tarball without publishing (for testing).

Bump version

$ npm version patch

Bump patch version (1.0.0 -> 1.0.1).

Bump minor version

$ npm version minor

Bump minor version (1.0.0 -> 1.1.0).

Bump major version

$ npm version major

Bump major version (1.0.0 -> 2.0.0).

Deprecate package

$ npm deprecate <package>@<version> "message"

Mark package version as deprecated.

Unpublish version

$ npm unpublish <package>@<version>

Remove specific version (discouraged).