Skip to main content
Publish packages and modules to the npm registry. Each target is packed with bun pm pack (so workspace dependencies resolve to real version ranges), extracted into dist/publish, and published with npm publish. Versions already present on the registry are skipped, so the command is safe to re-run. Publishing requires npm credentials saved with npm:credentials:create.

​
Usage

talos npm:publish [options]

​
Examples

Publish every package and module in the workspace: 
talos npm:publish
Publish specific packages (comma-separated): 
talos npm:publish --packages=cli,logger
Publish specific modules: 
talos npm:publish --modules=billing,catalog
Publish as a restricted (private) package: 
talos npm:publish --packages=cli --access=restricted

​
Options

OptionDescriptionDefault
--packagesComma-separated package names to publish (under packages/).All packages and modules
--modulesComma-separated module names to publish (under modules/).All packages and modules
--accessnpm access level: public or restricted.public
--silentSuppress log output and the publishing spinner.false
With neither --packages nor --modules, every directory under packages/ and modules/ is treated as a target. A target whose package.json version already exists on the registry is reported as ignored rather than re-published. At the end the command prints a summary of how many targets were published versus ignored.