mir-backend-bun

Solid

Make It Right (Bun runtime tier). Bun 1.3 reliability footguns shared across every Bun backend (Bun.serve, Hono, Elysia, or Express under bun) - Bun is a separate runtime on JavaScriptCore, not a faster Node. Covers: Node API gaps that present as silent stubs rather than errors, caught in CI or not at all; native addons that require() cleanly then abort on first real use; Bun.serve defaults that differ from node:http (10s idleTimeout that kills SSE, development:true leaking source in 500 pages); the single-thread model and silently ignored worker_threads options; bun:test running every file in ONE process with leaking globals; the text bun.lock and the blocked-install-scripts default. Chains: mir-backend -> this -> framework module. TRIGGER when the service runs on Bun in production, or when a Node-deployed project uses bun install / bun test in CI (then only the lockfile, install-script, and test sections apply). SKIP when the production runtime is Node.js with npm/pnpm/yarn - that is mir-backend-node, which

AI & Automation 15 stars 0 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
40
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /mir-backend-bun · Make It Right (Bun runtime) The middle tier. `mir-backend` decides **what is correct** (any language). A framework module knows the **library's mechanics**. This tier owns what is true for **every Bun backend because it runs on JavaScriptCore with Bun's own I/O layer and package manager** — not on V8, and not on Node's standard library. Bun is a distinct runtime that implements a large part of Node's API. It is not a Node flavour. Everything below is about the places that distinction costs you. Load order: `mir-backend` → `mir-backend-bun` → `<framework module, if any>`. ## Runtime state (verified 13 Aug 2026) | Release | Status | Notes | |---|---|---| | Bun **1.3.14** (2026-05-13) | current stable | `latest` on npm and the newest GitHub release. No newer release in the three months to 13 Aug 2026 | | Bun 1.3.13 | previous patch | the build every behaviour in this file was tested against (macOS arm64) | | Bun 1.3.0 (2025-10-10) | the 1.3 line | isolated installs default for workspaces, `Bun.SQL`, built-in Redis client, Security Scanner API, `test.concurrent` | | Bun 1.2 | superseded | switched the lockfile from binary `bun.lockb` to text `bun.lock` | **The support model is "upgrade to newest".** There is no published LTS line, no end-of-life calendar, and no scheduled security-release train the way Node has. Pin an exact version in CI and your image, and own the upgrade cadence yourself. **Advisories:** the GitHub Advisory Database lists one real B...

Details

Author
anantbhandarkar
Repository
anantbhandarkar/make-it-right
Created
3 months ago
Last Updated
1 weeks ago
Language
Python
License
Apache-2.0

Integrates with

Redis · Database FastAPI · Backend

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

mir-backend-bun-hono

Make It Right (Hono module). Hono 4 reliability augmentation for backends on the Web-standard Request/Response model - Bun, Cloudflare Workers, Deno, and Node via @hono/node-server. Footguns the runtime tiers omit: the request body is a stream read once, so c.req.raw throws after a validator ran; use cloneRawRequest; `await next()` never throws, so try/catch cleanup middleware sees nothing and the error lands in c.error instead; validator() parses but does not authorize, and yields an empty object when Content-Type is missing; the hono/bun vs hono/cloudflare-workers adapter split, where Node built-ins, the filesystem, and module-scope state work on Bun and fail on Workers. Plus 2026 advisories: CORS credentials-with-wildcard origin reflection (CVE-2026-54290, HIGH). Chains: mir-backend -> mir-backend-bun (or mir-backend-node when served through @hono/node-server) -> this. TRIGGER only when the web framework is Hono - a Hono route, middleware, validator, RPC client, adapter, or stream handler, on any runtime.

15 Updated 1 weeks ago
anantbhandarkar
AI & Automation Listed

bun-runtime

Use when running, testing, or deploying projects with Bun, or migrating from Node. Covers the bun.lock vs bun.lockb version change, Bun.serve/Bun.file/bun:test APIs, key CLI flags, Node compatibility, and Vercel setup.

1 Updated 1 weeks ago
Mixard
AI & Automation Listed

bun-runtime

Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

51 Updated yesterday
Fmarzochi