bun pm pack creates tarball
bun pm pack creates a tarball of the package in the current directory, displaying total files, shasum, integrity hash, unpacked size, and packed size.
Bun · Package manager · all subjects
publish: core behavior & flags
6 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 replaces catalog: with resolved versions
When you run bun publish or bun pm pack, Bun replaces catalog: references in your package.json with the resolved version numbers. The published package includes regular semver strings and no longer depends on your catalog definitions.
bun publish basic syntax and behavior
bun publish packs your package into a tarball and strips catalog and workspace protocols from the package.json, resolving versions if necessary. It then publishes to the registry specified in your configuration files. Both bunfig.toml and .npmrc files are supported. The basic syntax is `bun publish` from the current working directory to publish the package.
bun publish with tarball path
You can pack and publish separately by running `bun pm pack` to create a tarball, then `bun publish ./package.tgz` with the path to the output tarball. This allows you to pack first and publish the tarball later.
bun publish lifecycle scripts behavior
bun publish does not run lifecycle scripts (prepublishOnly/prepack/prepare/postpack/publish/postpublish) if you provide a tarball path. Lifecycle scripts run only when bun publish packs the package itself.
bun publish example output
When running `bun publish`, the output shows the packed files with their sizes, total file count, shasum, integrity hash, unpacked size, packed size, tag, access level, registry URL, and a summary line showing the package name and version being published with a + prefix.