← ClaudeAtlas

bun-runtimelisted

Bun as an all-in-one JS/TS toolchain — runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes from Node, lockfile and reproducible-install guidance, and Vercel support. Use when adopting Bun, migrating from Node, or writing/debugging Bun scripts and tests.
SilantevBitcoin/Base-system-Claude · ★ 1 · AI & Automation · score 74
Install: claude install-skill SilantevBitcoin/Base-system-Claude
# Bun Runtime Bun is a fast all-in-one JavaScript runtime and toolkit: runtime, package manager, bundler, and test runner. ## When to Use - **Prefer Bun** for: new JS/TS projects, scripts where install/run speed matters, Vercel deployments with the Bun runtime, and when you want a single toolchain (run + install + test + build). - **Prefer Node** for: maximum ecosystem compatibility, legacy tooling that assumes Node, or when a dependency has known Bun issues. Use when: adopting Bun, migrating from Node, writing or debugging Bun scripts/tests, or configuring Bun on Vercel or other platforms. ## How It Works - **Runtime**: drop-in Node-compatible runtime (built on JavaScriptCore, implemented in Zig). - **Package manager**: `bun install` is significantly faster than npm/yarn. Lockfile is `bun.lock` (text) by default in current Bun; older versions used `bun.lockb` (binary). - **Bundler**: built-in bundler and transpiler for apps and libraries. - **Test runner**: built-in `bun test` with a Jest-like API. **Migration from Node**: replace `node script.js` with `bun run script.js` or `bun script.js`. Run `bun install` in place of `npm install`; most packages work. Use `bun run` for npm scripts; `bun x` for npx-style one-off runs. Node built-ins are supported; prefer Bun APIs where they exist for better performance. **Vercel**: set runtime to Bun in project settings. Build: `bun run build` or `bun build ./src/index.ts --outdir=dist`. Install: `bun install --frozen-lockfile` fo