new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Bun · Package manager · all subjects

publish: flags & options

8 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

bun publish --access flag

The --access flag sets the access level of the package being published, either public or restricted. Unscoped packages are always public, and publishing an unscoped package with --access restricted is an error. The --access flag can also be set in the publishConfig field of package.json.

bun publish --tag flag

The --tag flag sets the tag of the package version being published. By default, the tag is latest. The initial version of a package is always given the latest tag in addition to the specified tag. The --tag flag can also be set in the publishConfig field of package.json.

bun publish --dry-run flag

The --dry-run flag runs the publish process without publishing the package, allowing you to verify what would be published.

bun publish --tolerate-republish flag

The --tolerate-republish flag causes bun publish to exit with code 0 instead of 1 if the package version already exists. This is useful in CI/CD environments where jobs may be re-run.

bun publish --gzip-level flag

The --gzip-level flag sets the gzip compression level used when packing the package, from 0 to 9 with default 9. This flag only applies to bun publish without a tarball path argument.

bun publish --auth-type flag

The --auth-type flag tells the npm registry which authentication method you prefer when 2FA is enabled for your npm account. Options are web (the default) or legacy. When set to legacy, bun publish prompts you for a one-time password in the CLI.

bun publish --otp flag

The --otp flag allows you to provide a one-time password directly to the CLI. If the password is valid, bun publish skips the extra one-time password prompt before publishing.

bun publish NPM_CONFIG_TOKEN environment variable

bun publish respects the NPM_CONFIG_TOKEN environment variable, which is useful when publishing from GitHub Actions or other automated workflows.

Give your agent this brain