Bun runtime: adopt, migrate from Node, run tests
Decide when to use Bun over Node, migrate a project from npm to Bun, and run, test and deploy Bun apps including on Vercel
- What
- Decide when to use Bun over Node, migrate a project from npm to Bun, and run, test and deploy Bun apps including on Vercel
- Cost
- Free
- Needs
- a JS/TS project (new or existing), Bun installed (bun.sh) if you want to run anything; Vercel account optional for the deployment section
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's Bun runtime playbook: a practical guide for the agent on when to pick Bun over Node (new JS/TS projects, install/run speed, single toolchain) and when to stay on Node (ecosystem compatibility, legacy tooling), with migration notes (bun install, bun run, Bun APIs, bun.lock/bun.lockb) and Vercel deployment specifics (runtime setting, build and frozen-lockfile installs). Includes ready-to-paste run/install/test commands and the built-in Bun.serve and Bun.file APIs. Honest caveat: the migration notes are written against current Bun — lockfile defaults and Bun/Node compat can drift, so re-verify against the Bun docs on a real migration. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Bun runtime is a free Muse skill for deciding when to use Bun over Node, migrating from npm to Bun, and running and deploying Bun apps including on Vercel. Choose Bun for new projects and speed, and stay on Node for ecosystem compatibility.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a JS/TS project (new or existing), Bun installed (bun.sh) if you want to run anything; Vercel account optional for the deployment section Install "Bun runtime: adopt, migrate from Node, run tests" for me. A practical guide for the agent: when to choose Bun vs Node (Bun for new JS/TS projects, speed, single toolchain; Node for ecosystem compatibility and legacy tooling), how to migrate (bun install, bun run, bun x, Bun APIs, bun.lock), plus Vercel specifics (runtime setting, frozen-lockfile deploys). Repository: https://raw.githubusercontent.com/affaan-m/ecc/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/.agents/skills/bun-runtime/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "bun-runtime". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install Bun from bun.sh if not already present). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
What the scan found — excerpts from the install prompt
- runs commands — Install "Bun runtime: adopt, migrate from Node, run tests" for me. A practical guide for the agent: when to ch · Installe-moi « Runtime Bun : adopter, migrer depuis Node, lancer des tests ». Un guide pratique pour l'agent :
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.