bun-runtime · secondsky — Claude Code skill: Bun CLI flags and bunfig.toml
A skill that teaches your agent the Bun runtime: running files, watch and hot modes, env vars, CLI flags and module resolution.
npx skills add secondsky/claude-skills --skill bun-runtime -a claude-codeWhat bun-runtime does
The skill hands your agent a reference for Bun, the JavaScriptCore-based runtime. It covers running files (bun run index.ts and the shorthand), the --watch, --hot, --smol, --inspect, --preload, --env-file and -e flags, and package.json scripts including bun run --bun vite. One section spells out flag placement: put them right after bun, or they get forwarded to your script instead.
Tables cover globals (Bun, Buffer, process, fetch, WebSocket), the difference between watch and hot, environment file loading, and common errors such as Cannot find module and top-level await. For deeper work the skill points to references/bunfig.md, references/cli-flags.md and references/module-resolution.md — load those when you configure bunfig.toml, set path aliases or debug import failures.
No API keys, no extra services. You need Bun in the project. If you are on Node.js and staying there, this skill has nothing for you — it describes Bun's behaviour, not Node's.
What it helps with
- run TypeScript or JSX without a separate build step
- restart the server when files change
- keep connections alive across reloads with hot mode
- load
.env.productioninstead of the auto-detected file - figure out why
--watchnever fires
Example prompts for the agent
- Why doesn't
bun run dev --watchrestart my server? - How do I load env vars from
.env.productionin Bun? - Set up
bunfig.tomlwith a preload script at./setup.ts
How to install bun-runtime
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill bun-runtime -a claude-code2Manually: put the files in place
~/.claude/skills/bun-runtime/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bun-runtime/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill bun-runtime -a codex2Manually: put the files in place
.agents/skills/bun-runtime/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill bun-runtime -a cursor2Manually: put the files in place
.cursor/skills/bun-runtime/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install secondsky/claude-skills bun-runtime2Manually: put the files in place
.github/skills/bun-runtime/SKILL.md1Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill bun-runtime -a gemini-cli2Platform CLI
gemini skills install https://github.com/secondsky/claude-skills --path plugins/bun/skills/bun-runtimeManually: put the files in place
.devin/skills/bun-runtime/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add secondsky/claude-skills --skill bun-runtime -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bun-runtime
How do I install bun-runtime in Claude?
Run npx skills add secondsky/claude-skills --skill bun-runtime -a claude-code. The skill file then lives at ~/.claude/skills/bun-runtime/SKILL.md.
What does bun-runtime do?
It tells your agent how to run code under Bun: CLI flags, watch and hot modes, environment variables, preload scripts, workspaces and module resolution.
What is the difference between --watch and --hot?
--watch restarts the whole process on file changes. --hot swaps modules and preserves state, so open connections and in-memory data survive.
Source text
SKILL.md · MIT
---
name: bun-runtime
description: Use for Bun runtime, bunfig.toml, watch/hot modes, env vars, CLI flags, and module resolution.
metadata:
version: "1.0.0"
license: MIT
---
# Bun Runtime
Bun is a fast all-in-one JavaScript runtime built on JavaScriptCore (Safari's engine). It provides 4x faster startup than Node.js on Linux.
## Quick Start
```bash
# Run a file
bun run index.ts
bun index.ts # shorthand
# Run with watch mode
bun --watch run index.ts
# Run package.json script
bun run dev
# Run with hot reloading
bun --hot run server.ts
```
## Core CLI Flags
| Flag | Purpose |
|------|---------|
| `--watch` | Restart on file changes |
| `--hot` | Hot module replacement (preserves state) |
| `--smol` | Reduce memory usage (slower GC) |
| `--inspect` | Enable debugger |
| `--preload` | Load modules before execution |
| `--env-file` | Load specific .env file |
| `-e, --eval` | Evaluate code string |
## Running Files
Bun transpiles TypeScript and JSX on-the-fly:
```bash
bun run index.js
bun run index.ts
bun run index.jsx
bun run index.tsx
```
**Important**: Put Bun flags immediately after `bun`:
```bash
bun --watch run dev # Correct
bun run dev --watch # Wrong - flag passed to script
```
## Package.json Scripts
```bash
# Run script
bun run dev
bun dev # shorthand (if no Bun command conflicts)
# List available scripts
bun run
# Run with Bun instead of Node
bun run --bun vite
```
Bun respects lifecycle hooks (`preclean`, `postclean`, etc.).
## Watch Mode vs Hot Reloading
| Mode | Flag | Behavior |
|------|------|----------|
| Watch | `--watch` | Full process restart on changes |
| Hot | `--hot` | Replace modules, preserve state |
```bash
# Watch mode - full restart
bun --watch run server.ts
# Hot reloading - preserves connections/state
bun --hot run server.ts
```
## Environment Variables
Bun automatically loads `.env` files:
```bash
# Loads automatically: .env, .env.local, .env.development
bun run index.ts
# Specify env file
bun --env-file .env.production run index.ts
# Disable auto-loading
# In bunfig.toml: env = false
```
Access in code:
```typescript
const apiKey = process.env.API_KEY;
const bunEnv = Bun.env.NODE_ENV;
```
## Globals Available
| Global | Source | Notes |
|--------|--------|-------|
| `Bun` | Bun | Main API object |
| `Buffer` | Node.js | Binary data |
| `process` | Node.js | Process info |
| `fetch` | Web | HTTP requests |
| `Request/Response` | Web | HTTP types |
| `WebSocket` | Web | WebSocket client |
| `crypto` | Web | Cryptography |
| `console` | Web | Logging |
| `__dirname` | Node.js | Current directory |
| `__filename` | Node.js | Current file |
## Preload Scripts
Load modules before your main script:
```bash
bun --preload ./setup.ts run index.ts
```
Or in `bunfig.toml`:
```toml
preload = ["./setup.ts"]
```
Use cases: polyfills, global setup, instrumentation.
## Stdin Execution
```bash
# Pipe code to Bun
echo "console.log('Hello')" | bun run -
# Redirect file
bun run - < script.js
```
## Workspaces & Monorepos
```bash
# Run script in specific packages
bun run --filter 'pkg-*' build
# Run in all workspaces
bun run --filter '*' test
```
## Debugging
```bash
# Start debugger
bun --inspect run index.ts
# Wait for debugger connection
bun --inspect-wait run index.ts
# Break on first line
bun --inspect-brk run index.ts
```
Connect via Chrome DevTools or VS Code.
## Common Errors
| Error | Cause | Fix |
|-------|-------|-----|
| `Cannot find module` | Missing dependency | Run `bun install` |
| `Top-level await` | Using await outside async | Wrap in async function or use `.mts` |
| `--watch not working` | Flag in wrong position | Put flag before `run` |
## When to Load References
Load `references/bunfig.md` when:
- Configuring bunfig.toml
- Setting up test configuration
- Configuring package manager behavior
- Setting JSX options
Load `references/cli-flags.md` when:
- Need complete CLI flag reference
- Configuring advanced runtime options
- Setting up debugging
Load `references/module-resolution.md` when:
- Troubleshooting import errors
- Configuring path aliases
- Understanding Bun's resolution algorithm
© secondsky · MIT · secondsky/claude-skills
Similar skills
All skills for Programming languages →bun-runtime by other authors comes first.