Claude Agent Skill · by Affaan M

Bun Runtime

Install Bun Runtime skill for Claude Code from affaan-m/everything-claude-code.

Works with Paperclip

How Bun Runtime fits into a Paperclip company.

Bun Runtime drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md84 lines
Expand
---name: bun-runtimedescription: Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.origin: ECC--- # 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 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 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` for reproducible deploys. ## Examples ### Run and install ```bash# Install dependencies (creates/updates bun.lock or bun.lockb)bun install # Run a script or filebun run devbun run src/index.tsbun src/index.ts``` ### Scripts and env ```bashbun run --env-file=.env devFOO=bar bun run script.ts``` ### Testing ```bashbun testbun test --watch``` ```typescript// test/example.test.tsimport { expect, test } from "bun:test"; test("add", () => {  expect(1 + 2).toBe(3);});``` ### Runtime API ```typescriptconst file = Bun.file("package.json");const json = await file.json(); Bun.serve({  port: 3000,  fetch(req) {    return new Response("Hello");  },});``` ## Best Practices - Commit the lockfile (`bun.lock` or `bun.lockb`) for reproducible installs.- Prefer `bun run` for scripts. For TypeScript, Bun runs `.ts` natively.- Keep dependencies up to date; Bun and the ecosystem evolve quickly.