Architecture
Design principles, contracts, router and DI internals, package hierarchy, RFCs/ADRs, and versioning.
This section explains how NextRush works internally — the design decisions behind the public API, the actual data structures and algorithms inside the router and DI container, the contracts Extensions and adapters must satisfy, and the project's honest state on RFCs and versioning. If you're looking for how to use a feature, see Concepts or Guides instead — this section is for understanding or contributing to the framework itself.
Design Principles
Minimal core, explicit over implicit, zero dependencies — verified against source and README.
Contracts
The Extension API contract and the Adapter Contract — the two structural interfaces framework authors implement against.
Router Internals
The segment trie's real node structure, match priority, and audited edge cases.
Capability Composition
How middleware, registrars, Extensions, and adapters compose into one running app.
Package Hierarchy
Dependency order and a dependency graph generated from every package.json, not hand-drawn.
Dependency Injection Internals
How @nextrush/di wraps tsyringe — scope mapping, cycle detection, and the tsyringe coupling boundary.
Middleware Internals
The compose() engine — dispatch mechanics, error propagation, and the callback() pipeline.
Adapter Internals
What the cross-adapter conformance suite actually enforces across Node, Bun, Deno, Edge, and serverless.
RFCs & ADRs
Design proposals and the durable decisions promoted from them.
Versioning & Compatibility
The mixed-version split across published packages, verified per package.json.
Release Handbook
How a release actually ships — CLI vs. CI, the full Changesets lifecycle, and every real mistake found running it.
Looking for the contributor workflow (build, test, PR process)? See Contributing — it moved out of this section because it's about working on the repo, not about how the framework itself works.