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

remove: core behavior

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 remove basic syntax

bun rm <package> removes a dependency from the project.

bun remove basic syntax

The basic syntax for bun remove is 'bun remove <package-name>'. For example, 'bun remove ts-node' removes the ts-node package from the project.

bun remove aliases

The bun remove command has three aliases: 'bun rm', 'bun uninstall', and 'bun r'. All four commands are functionally equivalent.

bun remove updates all dependency groups

When you run bun remove, Bun removes the package from every dependency group in package.json that lists it and updates bun.lock. Once nothing else depends on the package, Bun deletes it from node_modules.

bun remove --filter in monorepos

The --filter flag (alias -F) removes a package from matching workspace(s) in a monorepo instead of the current directory's package. It uses the same patterns as 'bun add --filter'. Use '--filter '*'' to remove the package from every workspace package. Workspaces that don't list the package are left untouched.

bun remove --filter examples

Example usage of bun remove with --filter: 'bun remove zod --filter api' removes zod from the api workspace, and 'bun remove zod --filter '*'' removes zod from every workspace package.

Give your agent this brain