Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Bun Runtime Migration
Migrate a Node.js project to Bun
Move backend scripts, CI test runners and dev tooling from Node.js to the Bun runtime, without breaking production. The skill brings a disciplined, incremental migration: a compatibility matrix triage, native-addon audit, lockfile migration strategy and a CI/CD switch, so you capture Bun's faster installs, ~10x faster test runs and lower startup latency only where it's safe, with a rollback plan at every step.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Moving to Bun is a gated engineering decision with rollback at every stage, never a trend jump. The sequence runs from scope checks and dependency triage to two weeks of parallel lockfiles before CI flips.
- Scope gate first: only backend scripts, CI test runners and dev tooling qualify; Vercel Next.js production builds, n8n core and Expo metro bundling stay on Node and npm, no exceptions.
- Runs the pre-flight script: Bun version check, module type, native addon scan (sharp, bcrypt, sqlite3, canvas with known verdicts per platform), lockfile backup, then bun install --dry-run; any incompatible package stops the migration cold.
- Triages every dependency into blocker, workaround or wontfix: blockers get alternatives (bun:sqlite instead of sqlite3, bcryptjs instead of bcrypt) or the migration is deferred with the reason recorded.
- Migrates in four incremental stages, each with rollback ready: bun install, then bun run dev, then bun test (resolving jest-to-bun mock API differences), and only after all three pass, the CI workflow switch.
- Runs lockfiles in parallel for two weeks: package-lock.json and bun.lockb both committed, divergence checked with bun pm ls against npm ls, and the npm lockfile retires only at zero divergence.
- Flips CI with oven-sh/setup-bun@v2: cache keyed on the bun.lockb hash, --frozen-lockfile mandatory to catch drift, bunx tsc --noEmit as a separate type-check step, and hyperfine benchmarks document the actual install, test and startup gains.
One power source. 6 lines out.
bun-runtime-migration · core
core active · 6 lines
- ✓ lowering cron-job startup
Lowering cron-job startup latency on backend servers
- ✓ cutting ci minutes by mo…
Cutting CI minutes by moving from jest to bun test
- ✓ speeding up dependency i…
Speeding up dependency installs (from ~90s toward ~25s)
- ✓ auditing native addons (…
Auditing native addons (sharp, bcrypt, sqlite3) for Bun compatibility
- ✓ planning a package-lock.…
Planning a package-lock.json to bun.lockb lockfile migration
- ✓ benchmarking npm vs bun
Benchmarking npm vs bun install/test/build with hyperfine
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Capture faster installs, tests and startup only where it's proven safe
license: perpetual -
Avoid production breakage with a 4-stage incremental migration path
license: perpetual -
Keep a rollback ready at every stage (parallel lockfile and node_modules)
license: perpetual -
Make a measured KABUL/ERTELE/RED decision instead of chasing a trend
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
bunfig.toml, package.json scripts and lockfile comparison reference
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Backend and platform engineers evaluating Bun for cron jobs, CI test runners and internal tooling who need the speed gains without risking production stability.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
Do my existing Node scripts run on Bun, or is this a rewrite?
For the scripts, CI runners, and dev tooling this targets, most run as-is since Bun aims for Node compatibility. The migration is about swapping the runtime and catching the edges, not rewriting your logic.
-
Bun is fast, but is it safe to put in front of production?
That's why the scope here is deliberately cron jobs, CI test runners, and internal tooling, the low-blast-radius surfaces. It moves the fast wins first 'without breaking production,' rather than betting your live server on a runtime swap.
-
Can I migrate my whole production app server to Bun with this?
No, and that's the honest limit. Bun isn't a full drop-in where you lean on native Node addons or less-common Node APIs, so this stays at the edges and leaves the production runtime decision out of scope.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.