mir-backend-nodelisted

Make It Right (Node.js runtime tier). V8/Node 22–26 runtime reliability footguns that are shared across EVERY Node backend framework (Express, Fastify, NestJS, Hapi, Koa) — distinct from the generic backend gates and from any one framework's mechanics. Covers: the single-threaded event loop and what blocks it (sync I/O, huge JSON, synchronous crypto/zlib, long CPU loops, pathological regex), the absence of CPU parallelism on one process and how to get it (worker_threads / cluster), unhandled promise rejection crashes, serializing awaits in a loop vs. bounded Promise.all concurrency, stream backpressure, AbortSignal.timeout on every outbound call, uncaughtException semantics, heap limits under container memory, graceful shutdown with keep-alive sockets, async-context loss across callbacks and timers, require(esm) and native TypeScript type stripping, and npm supply-chain defaults after the 2025–2026 registry compromises. TRIGGER when the backend runtime is Node.js / V8 — sits between mir-backend (generic gates
anantbhandarkar/make-it-right · ★ 15 · API & Backend · score 81

Install: claude install-skill anantbhandarkar/make-it-right

# /mir-backend-node · Make It Right (Node.js runtime) The middle tier. `mir-backend` decides **what is correct** (any language). The framework module (e.g. `mir-backend-node-express`) knows the **library's mechanics**. This tier owns what's true for **all Node backends because they run on V8 in a single-threaded event loop** — the concurrency model and process model that Express, Fastify, NestJS, and every other Node framework all inherit. Load order: `mir-backend` → `mir-backend-node` → `<framework module>`. ## Runtime floor (checked against nodejs.org, 13 Aug 2026) | Line | Status | Notes | |---|---|---| | Node 26 | Current | latest 26.7.0; enters LTS Oct 2026. Not the production default yet. | | Node 24 "Krypton" | **Active LTS** | latest 24.19.0. The default target for new services. | | Node 22 "Jod" | Maintenance LTS | latest 22.23.2; EOL 2027-04-30. Acceptable floor for existing services. | | Node 20 "Iron" | **End of life** | EOL 2026-04-30. Gets no security patches. Do not target it. | | Node 18 | End of life | EOL 2025-04-30. | **Older versions of this skill said "Node 20+ LTS". That is now wrong** — Node 20 stopped receiving security releases on 2026-04-30 and was explicitly excluded from the July 2026 security release. State **Node 22 minimum, Node 24 recommended** in `engines.node` and in the Dockerfile base image. The Node project has announced that the odd/even release model ends with Node 27 (every line will enter LTS after its Current phase). Do not plan