Help us improve
Share bugs, ideas, or general feedback.
From bun
Provides Bun runtime patterns for bunx execution, lockfile handling, module resolution, shell scripting with Bun.$, subprocess spawning, file I/O, and bun test usage.
npx claudepluginhub bendrucker/claude --plugin bunHow this skill is triggered — by the user, by Claude, or both
Slash command
/bun:bunThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `--bun` before the executable name to force the Bun runtime over Node shebangs. Use `-p`/`--package` when the binary name differs from the package name (e.g., `bunx -p @angular/cli ng`).
Guides fast JavaScript/TypeScript development with Bun runtime: project init, package management, built-in bundler/test runner, Node.js migration, and troubleshooting.
Runs Bun scripts, tests with compact reporters and bail flags, builds bundles/executables, and initializes projects using flags for fast feedback and minimal output.
Guides Bun runtime usage including CLI flags (--watch, --hot), watch/hot modes, env vars and .env files, bunfig.toml config, package.json scripts, and module resolution.
Share bugs, ideas, or general feedback.
Use --bun before the executable name to force the Bun runtime over Node shebangs. Use -p/--package when the binary name differs from the package name (e.g., bunx -p @angular/cli ng).
bun.lock is a text-based lockfile. Resolve merge conflicts by deleting it and running bun install to regenerate from scratch — never attempt to merge lockfile contents.
Runtime flags must precede the script path: bun --cwd ./packages/app run dev. Never use .js extensions in TypeScript imports — Bun resolves them natively.
Bun.$ is a tagged template for shell execution. Use response methods (.text(), .json(), .lines()) to extract output, .nothrow() to handle failures without exceptions, and pipe/redirect syntax for composing commands.
Bun.spawn spawns subprocesses with streaming I/O. Use Bun.spawnSync for synchronous execution. Configure stdin/stdout/stderr, environment variables, and working directory. Check exitCode for error handling.
Bun.file() creates file handles with .text(), .json(), .arrayBuffer(), and .stream() methods. Bun.write() writes content to files or stdout/stderr. Both support streaming for large files.
Bun runs tests in a single process. Use describe/it/test for structure, expect matchers for assertions, lifecycle hooks (beforeEach, afterEach) for setup/teardown, mock() for function mocking, and .toMatchSnapshot() for snapshot testing. Set AGENT=1 to suppress passing test output.