Open a terminal in the package workspace.

Confirm the working tree contains only the intended changes:

git status
git diff

Check that all runtime imports are declared in dependencies or peerDependencies.

Choose a new, unused version number. Published npm versions cannot be overwritten.

Beta example:

22.0.0-beta.1

Stable example:

22.0.0

Update the version in the package’s package.json.

Install dependencies:

npm install

Run the package tests, if available:

npm test

Create a production build:

npm run build

Inspect the generated package’s package.json. Verify:

• Package name
• Version
• Dependencies and peer dependencies
• Public access configuration
• Exported entry points

Run a publish dry-run.

For a beta:

npm publish --dry-run --tag beta

For a stable release:

npm publish --dry-run

Review the dry-run output and ensure no source files, secrets, local configuration, or unnecessary files are included.

Verify npm authentication and package ownership:

npm whoami
npm owner ls <package-name>

Confirm that the version does not already exist:

npm view <package-name>@<version> version

A 404 means the version is still available.

Publish the package.

Beta release:

npm publish --tag beta

Stable release:

npm publish

Complete npm’s browser or one-time-password authentication when requested.

Verify the distribution tags:

npm view <package-name> version dist-tags --json

For a beta release, confirm that:

• beta points to the new prerelease.
• latest still points to the existing stable version.

Verify the installed version:

npm ls <package-name> --depth=0

Build and test the consuming application.

Commit the version and package configuration changes.

Document the published version and any important release notes.