All Packages (A-Z)
Every publishable NextRush package in one alphabetical index, tagged by capability category and linked to its API reference.
Every publishable package, searchable and filterable by category. This table renders directly
from the package registry — the same source /packages and the sidebar's capability groups
read from — so it can never drift out of sync with the real package set. For the dependency
chain and package tiers, see Package Hierarchy.
Showing 35 of 35 packages
Core
7 packages@nextrush/corev3.1.0Application, Context, and middleware composition — the framework entry point.
@nextrush/errorsv3.1.0Standardized HTTP error class hierarchy for the whole framework.
@nextrush/runtimev3.1.0Runtime detection and cross-runtime abstractions used by adapters.
@nextrush/streamv3.1.0Runtime-agnostic response streaming (text, SSE, NDJSON) for AI/agentic apps.
@nextrush/typesv3.1.0Shared TypeScript types used across every NextRush package.
Class Runtime
3 packages@nextrush/classv3.1.0Consolidated class runtime — decorators, DI re-export, controllers, modules, guards, interceptors, filters, and lifecycle hooks.
@nextrush/testingv1.0.0Test harness with DI isolation for class-based controllers and services.
Security
4 packages@nextrush/corsv3.1.0CORS header middleware with configurable origin, method, and header allow-lists.
@nextrush/csrfv1.0.0CSRF protection via the signed double-submit cookie pattern with HMAC-SHA256.
@nextrush/helmetv3.1.0Security headers middleware (CSP, HSTS, X-Content-Type-Options, and more).
Request Data
4 packages@nextrush/body-parserv3.1.0JSON, form, and text request body parsing middleware.
@nextrush/cookiesv1.0.0Cookie parsing and serialization middleware.
@nextrush/form-datav1.0.0Streaming multipart/form-data parser and file upload middleware.
Responses
4 packages@nextrush/compressionv3.1.0Response compression middleware with Gzip, Brotli, and Deflate support.
@nextrush/openapiv1.0.0Zero-config OpenAPI 3.1 generation from route validation metadata.
@nextrush/staticv1.0.0Static file serving middleware.
@nextrush/templatev1.0.0Template rendering engine with helpers, partials, layouts, and streaming.
Observability
4 packages@nextrush/healthv1.0.0Liveness/readiness health check endpoints for orchestrator probes (Kubernetes, PM2, systemd).
@nextrush/loggerv1.0.0Structured request logging middleware.
@nextrush/request-idv1.0.0Request ID generation middleware for distributed tracing and correlation.
@nextrush/timerv1.0.0Response time tracking middleware.
Real-time & Events
2 packagesAdapters
5 packages@nextrush/adapter-bunv1.0.0Bun HTTP adapter.
@nextrush/adapter-denov1.0.0Deno HTTP adapter.
@nextrush/adapter-edgev1.0.0Edge runtime adapter for Cloudflare Workers, Vercel Edge, and similar platforms.
@nextrush/adapter-nodev3.1.0Node.js HTTP adapter — the default runtime target.
@nextrush/adapter-serverlessv1.0.0Serverless adapter for AWS Lambda, API Gateway, GCF, and Azure via a generic event-mapper registry.
Tooling
2 packagesCategory legend
| Category | Meaning |
|---|---|
| Core | Foundation packages (types, errors, core, router, runtime, stream) plus the nextrush meta package that re-exports them |
| Class Runtime | Decorators, DI, controllers, modules, guards, interceptors, filters (@nextrush/class, @nextrush/di) |
| Security | CORS, security headers, CSRF, and rate limiting middleware |
| Request Data | Body parsing, file uploads, cookies, and request validation middleware |
| Responses | Compression, static files, templates, and OpenAPI generation middleware |
| Observability | Logging, request IDs, and response-time tracking middleware |
| Real-time & Events | Long-lived, app-scoped services registered with app.extend() — WebSocket and the event emitter |
| Adapters | Runtime adapters — connect Application to a specific runtime's HTTP primitives (see the Adapter Contract) |
| Tooling | Build-time and CLI tooling, not runtime dependencies of a deployed app |
Keeping this index accurate
This table renders from apps/website/src/lib/package-registry.ts, not a hand-typed list — a
new package only needs a registry entry, never a second edit here. pnpm docs:verify-registry
fails the build if the registry and the real packages/**/package.json set ever disagree.