Help

Compatibility Matrix

Real, current package versions and Node.js/runtime requirements — re-derived directly from every package.json in the monorepo.

This table was generated by reading every workspace manifest in the repository directly — not copied from an earlier phase's registry — so it reflects the actual current state. NextRush intentionally runs a mixed-version monorepo: the fixed core group releases at 4.0.2, while packages added later version independently on their own 0.x–3.x semver lines. A 1.0.1 package is not less mature than a 4.0.2 one — it started its own semver line later. See Versioning for the policy.

Runtime requirement

All packages require Node.js >=22.0.0 (from the repository root package.json's engines field). Bun, Deno, and Edge targets are supported via dedicated adapter packages — they do not lower the underlying Node.js baseline used for tooling/build.

Fixed core group (4.0.2)

These packages are configured as one fixed group and always release together.

PackageVersionType
nextrush4.0.2Meta package
@nextrush/types4.0.2Core
@nextrush/errors4.0.2Core
@nextrush/core4.0.2Core
@nextrush/router4.0.2Core
@nextrush/runtime4.0.2Core
@nextrush/di4.0.2Core
@nextrush/adapter-node4.0.2Adapter

Independently-versioned packages

Each of these versions independently — a patch to one does not bump any other package.

PackageVersionType
@nextrush/adapter-bun1.0.1Adapter
@nextrush/adapter-deno1.0.1Adapter
@nextrush/adapter-edge1.0.1Adapter
@nextrush/adapter-nextjs1.0.1Adapter
@nextrush/adapter-serverless1.0.1Adapter
@nextrush/body-parser4.0.1Middleware
@nextrush/class1.0.2Class runtime
@nextrush/compression3.0.7Middleware
@nextrush/cookies1.0.1Middleware
@nextrush/cors4.0.1Middleware
@nextrush/csrf1.0.1Middleware
@nextrush/dev1.1.3Tooling
@nextrush/events1.0.1Extension
@nextrush/express-bridge0.1.1Interop
@nextrush/form-data1.0.1Middleware
@nextrush/health1.0.1Middleware
@nextrush/helmet4.0.1Middleware
@nextrush/logger2.0.0Middleware
@nextrush/openapi1.0.3Middleware
@nextrush/rate-limit1.0.1Middleware
@nextrush/request-id1.0.1Middleware
@nextrush/security1.0.1Middleware
@nextrush/static1.0.1Middleware
@nextrush/stream1.0.2Extension
@nextrush/template1.0.1Middleware
@nextrush/testing1.0.2Tooling
@nextrush/timer1.0.1Middleware
@nextrush/validation1.0.2Middleware
@nextrush/websocket1.0.1Extension
create-nextrush1.3.1Scaffolder

Total: 38 public packages. The monorepo has 52 workspace projects; the other 14 are private (including @nextrush/adapter-conformance, deployment-verification fixtures, and Next.js test apps) and are not published to npm.


Runtime support matrix

RuntimeAdapter packageAdapter versionStatusProof
Node.js 22+@nextrush/adapter-node4.0.2Stable🟢 real-runtime (native)
Bun@nextrush/adapter-bun1.0.1Stable🟢 real-runtime (CI, real Bun)
Deno@nextrush/adapter-deno1.0.1Stable🟢 real-runtime (CI, real Deno)
Cloudflare Workers@nextrush/adapter-edge1.0.1Beta (Internal tier)🟢 real-runtime (CI, real workerd/miniflare)
Vercel Edge@nextrush/adapter-edge1.0.1Beta (Internal tier)🟡 simulated (shares the edge adapter's conformance suite; not yet executed on the real platform in CI)
Netlify Edge@nextrush/adapter-edge1.0.1Beta (Internal tier)🟡 simulated (runs on Deno under the hood; not yet executed on the real platform in CI)
AWS Lambda / GCF / Azure Functions@nextrush/adapter-serverless1.0.1Beta (Internal tier)🟡 simulated (built on @nextrush/adapter-edge's fetch engine; not yet executed on a real serverless platform in CI)

What 🟢/🟡 means

🟢 real-runtime — the conformance suite executes on the actual runtime in CI (a real Bun/ Deno process, or a real Cloudflare workerd/miniflare isolate), not simulated under Node. 🟡 simulated — the adapter is implemented and passes the shared conformance suite, but that suite currently runs in-process under Node/vitest for this target, not on the real platform. See docs/audits/08-runtime-compatibility-gap-analysis.md for the full breakdown and the work tracked to close the remaining 🟡 rows.

Known, unresolved conflict with ADR-0005

This table classifies every non-Node adapter as Stable, based on adapter version and conformance-suite results. ADR-0005 classifies runtime and every non--node adapter as Internal — may change without a major bump, until GA, a stricter tier than "Stable" implies. This is a real, unresolved disagreement between two source-of-truth documents, first identified during Wave B1 of the v4 documentation rebuild — it is deliberately left logged here rather than silently resolved in either direction pending a maintainer decision. Readers relying on this page for a stability guarantee on Bun, Deno, Edge, or Serverless should also read ADR-0005's tier table before treating "Stable" as a semver commitment.


How to check this yourself

Version drift between this page and reality is a documentation bug. Re-derive the table with:

pnpm list -r --depth -1 --json | node -e "
let s = '';
process.stdin.on('data', (d) => (s += d)).on('end', () => {
  for (const p of JSON.parse(s)) if (!p.private) console.log(p.name + '\t' + p.version);
});
"

If your output differs from the table above, the table is stale — please open an issue.

See also

Was this helpful?

On this page