bun-runtime

Integrate Bun runtime APIs into tooling scripts for local automation.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/matthewharwood/dean-stack --skill bun-runtime-matthewharwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bun-runtime
Source: https://github.com/matthewharwood/dean-stack/tree/main/.claude/skills/bun-runtime
Command: npx skills add https://github.com/matthewharwood/dean-stack --skill bun-runtime-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bun-runtime solves the need for cleanly exposing Bun 1.3.13 runtime APIs to tooling and scripts within the dean-stack workflow, while clearly separating browser app bundling from server execution.

Core Features & Use Cases

  • Exposes Bun runtime APIs (Bun.serve, Bun.file, Bun.$) for scriptable automation.
  • Guides common tooling tasks such as bunx invocations, bun script workflows, and bun shell usage.
  • Enforces a deployment model where the production app remains static and client code is built by Vite, not Bun.

Quick Start

Configure your tooling to call Bun runtime APIs in scripts to automate local dev workflows.

Frequently Asked Questions about bun-runtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use Bun runtime APIs for local automation scripts?

To use Bun runtime APIs for local automation, integrate Bun.serve, Bun.file, and Bun.$ directly into your tooling scripts. This enables scriptable automation for build scripts, code generation, and one-off tooling tasks within your local development workflow.

Can I use Bun shell to automate build scripts and code generation?

Yes, Bun shell usage is supported for automating build scripts and code generation. You can invoke bunx commands and execute bun script workflows under the scripts/ directory to automate local development behaviors cleanly separated from production server logic.

Does Bun runtime work with Vite for building browser code?

Bun runtime works with Vite by enforcing a strict separation of concerns. Vite builds the static client-side browser code, while Bun runtime handles server execution and local tooling tasks, ensuring the production app remains a static build.

What is the best way to separate runtime tasks from production server behavior in Bun?

The best way to separate runtime tasks from production behavior is by confining Bun runtime API calls to tooling scripts under the scripts/ directory. This ensures browser code is built by Vite while runtime behaviors are invoked by Bun for local automation only.

Do I need version pinning to use Bun runtime in my tooling?

Explicit version pinning is supported for Bun runtime in your tooling, specifically targeting Bun 1.3.13. Pinning the version ensures consistent execution of Bun.serve, Bun.file, and Bun.$ APIs across your local development and automation environments.