npmの段階的公開が新規パッケージの作成に対応npm staged publishing now supports creating new packages

Create a new npm package

npm staged publishing can now create a new npm package through npm stage publish. The change matters for automated workflows because they no longer need a manual first publish before they can create a package.

Package creation can use either a local session or a granular access token. The supported token options include a stage-only token, allowing the package-creation step to be performed through staged publishing.

Public and private packages

The capability works across several package types. It supports public scoped packages, public unscoped packages, and private scoped packages.

This means staged publishing can be used to create a package in each of those supported forms, rather than requiring the package to exist before the staged process begins. An automated workflow can therefore create the new package and submit its first version through npm stage publish.

First version enters staged queue

Creating the package does not immediately make its first version available to install. Instead, the first version enters the staged queue.

A maintainer must promote that version before it becomes installable. The initial creation and submission can be automated, while promotion by a maintainer remains required for the first release to become available.

The staged queue therefore applies from the package’s first version. The workflow removes the need for a separate manual first publish, but it does not remove the maintainer promotion step.

After package creation

Once the package has been created, its settings can be managed and trusted publishing can be configured. These actions take place after the staged publishing process has established the package.

Feedback and discussion about what comes next are being directed to the npm roadmap discussion in GitHub Community. Additional tips, technical guides, and best practices are also available through a biweekly newsletter for developers.