NextRush

NextRush started as a from-scratch study of framework internals and grew into a real monorepo: 20+ packages under packages/ (core, router, di, decorators, runtime, types, errors, plus adapters for node/bun/deno/edge, 10 middleware packages, and 6 plugin packages), a Fumadocs-based documentation site, and a benchmark suite comparing it against Fastify, Express, Koa, and Hono.

The router is a segment trie — not a compressed radix tree, the two are often confused. Routes are indexed by path segment for O(d) lookup where d is segment depth; static routes get a separate hash map for O(1) lookup, and route executors are pre-compiled at registration time rather than per request. Dependency injection is an explicit, honest wrapper around tsyringe (Microsoft's DI library) rather than a from-scratch container — it adds circular-dependency detection and clearer error messages on top. Middleware follows the same Koa-style onion model as Express/Koa: (ctx, next) => Promise<void>, composed once at server-start time.

Benchmarking used autocannon across six frameworks (raw Node, Fastify, NextRush, Hono, Koa, Express) on identical hardware, with results committed to the repo as raw JSON, not just summarized in prose. The one place NextRush actually wins outright is the middleware-stack scenario — beating both Fastify and raw Node.js — which says more about pipeline design than about the router.

Two scoping notes worth being upfront about: the "under 3,000 LOC" and "zero dependencies" claims in the framework's own docs apply to the core/router/types/errors package group specifically, not the full 20+ package monorepo — the DI/decorators stack has two real runtime dependencies (tsyringe, reflect-metadata). And an internal architecture audit in the repo was self-conducted by an AI coding agent, not a third-party security review — it's a useful engineering artifact, but not independent validation.