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

add: core behavior & version specification

15 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 add basic syntax

Add a dependency with 'bun i <package>'. Add a dev dependency with 'bun i -d <package>'.

bun update to specific version

bun update <package>@<version> updates a dependency to a specific version.

Adding dependencies to individual workspaces

To add npm dependencies to a particular workspace, cd to that directory and run bun add as you normally would. Bun detects that you are in a workspace, adds the dependency to that workspace's package.json, and updates the root lockfile.

bun add --catalog adds to default catalog

bun add --catalog adds the entry to the root catalog and writes catalog: to the current package. bun add --catalog=<name> adds it to catalogs.<name> and writes catalog:<name>. Bun reuses an existing catalog entry unless you pass an explicit version.

bun add reuses catalog entry by default

Even without the --catalog flag, bun add react (no version specified) writes catalog: when the default catalog already lists react. Pass an explicit version to write a concrete range instead.

bun add basic syntax

To add a package, use `bun add <package-name>`. To specify a version, version range, or tag, use `bun add <package-name>@<version>`, such as `bun add zod@3.20.0`, `bun add zod@^3.0.0`, or `bun add zod@latest`.

bun add default behavior and dependency groups

Bun writes packages to `dependencies` by default unless you pass `--dev`, `--optional`, or `--peer`. If `package.json` already lists the package in another group, Bun updates that entry in place.

--exact flag pins package to resolved version

Use `--exact` or `-E` to pin a package to the resolved version. Bun writes the exact version number to `package.json` instead of a version range. For example, `bun add react --exact` writes `"react": "18.2.0"` instead of `"react": "^18.2.0"`. The exact version matches only that specific version, while `^18.2.0` matches >= 18.2.0 < 19.0.0.

--catalog flag for workspace catalogs

In a workspace, use `--catalog` to write the version to the root `package.json` catalog and add `"catalog:"` to the current package. Use `--catalog=<name>` for named catalogs from `workspaces.catalogs.<name>`, which writes `"catalog:<name>"`. Example: `bun add react --catalog` or `bun add vitest --catalog=testing`. If the catalog already has an entry, Bun reuses it and writes only `"catalog:"` to the current package. Pass an explicit version like `bun add react@19 --catalog` to replace the entry, which affects every package referencing it. Attach the name with `=`: `--catalog=testing`, not `--catalog testing`. Bun catalogs tarball and git specifiers under the package's real name and rejects relative paths and workspace packages.

bun add without version uses catalog if available

Even without the `--catalog` flag, `bun add react` (no version) writes `"catalog:"` if the default catalog already lists `react`. Pass a version to write a concrete range instead.

--filter flag for monorepo workspace targeting

Use `--filter` or `-F` to add a package to matching workspace(s) instead of the current directory. Repeat the flag to combine patterns; `!pattern` excludes. Example: `bun add zod --filter api`, `bun add -d typescript --filter './packages/*'`, or `bun add zod --filter '*' --filter '!api'`. The `*` pattern matches every workspace package but not the root; to include the root, name it explicitly. Bun resolves local paths from the current directory and rewrites them relative to each selected package. Bun updates `bun.lock` for the whole repo but links only the selected workspaces into `node_modules`. Cannot be combined with `--global`.

--global flag installs packages globally

Use `--global`, `-g`, `bun install --global`, or `bun install -g` to install a package globally. This does not modify the `package.json` of your current project. Use it to install command-line tools. Example: `bun add --global cowsay` or `bun add -g cowsay`.

Trusted dependencies for lifecycle scripts

By default, Bun does not execute lifecycle scripts for installed dependencies such as `postinstall`. To allow lifecycle scripts for a particular package, add the package name to the `trustedDependencies` array in `package.json`. Example: `"trustedDependencies": ["my-trusted-package"]`.

Install security scanner as dev dependency

Install a security scanner from npm using 'bun add -d' followed by the package name, for example: bun add -d @oven/bun-security-scanner.

save-exact option in .npmrc

The save-exact option in .npmrc always saves exact versions without the ^ prefix. Set save-exact=true to enable this behavior.

Give your agent this brain