Roadmap
Current development status and planned features for NextRush v3.
NextRush v3 development tracks what has shipped, what is actively being built, and what comes next. Each item below reflects the actual state of the codebase.
Priorities may shift based on community feedback. Items without code or an RFC are considered aspirational.
Current Status
Package versions: 3.0.4 (unified across @nextrush/*)
NextRush v3 packages are published on npm under semver 3.0.x. Breaking API changes require a major version bump; new features ship in minor releases when applicable.
Phase 1: Core Foundation ✅
Status: Complete
- Application core with middleware composition (
@nextrush/core) - Radix tree router (
@nextrush/router) - HTTP error hierarchy (
@nextrush/errors) - Shared type definitions (
@nextrush/types) - Runtime detection (
@nextrush/runtime) - Node.js adapter (
@nextrush/adapter-node)
Phase 2: Developer Experience ✅
Status: Complete
- Dependency injection container (
@nextrush/di) - Decorator system —
@Controller,@Get,@Body,@UseGuard(@nextrush/decorators) - Controllers plugin with auto-discovery (
@nextrush/controllers) - Guard system for route protection
- Dev tools CLI with hot reload and watch mode (
@nextrush/dev) - Meta package re-exporting core essentials (
nextrush)
Phase 3: Middleware & Plugins ✅
Status: Complete
Middleware
- CORS (
@nextrush/cors) - Security headers (
@nextrush/helmet) - Body parsing — JSON, URL-encoded, multipart (
@nextrush/body-parser) - Response compression (
@nextrush/compression) - Cookie handling (
@nextrush/cookies) - Rate limiting with pluggable store interface (
@nextrush/rate-limit) - Request ID generation (
@nextrush/request-id) - Request timing (
@nextrush/timer)
Plugins
- Logger (
@nextrush/logger) - Static file serving (
@nextrush/static) - Template engine (
@nextrush/template) - Event system (
@nextrush/events) - WebSocket support (
@nextrush/websocket)
Phase 4: Multi-Runtime Adapters ✅
Status: Complete
- Node.js adapter (
@nextrush/adapter-node) - Bun adapter (
@nextrush/adapter-bun) - Deno adapter (
@nextrush/adapter-deno) - Edge adapter — Cloudflare Workers, Vercel Edge (
@nextrush/adapter-edge)
Phase 5: Performance Validation 🚧
Status: In Progress
- Benchmarking suite comparing Express, Fastify, Hono, and Koa
- Published benchmark results with reproducible scripts
- Memory profiling and optimization pass
Planned
These items have no implementation yet. Some are tracked in RFCs; others are aspirational.
View all planned items
Middleware & Security
- Session management middleware
- CSRF protection middleware
- Built-in Redis store for rate limiting
Developer Tooling
- CLI command for project scaffolding (
nextrush init) - Security audit and dependency scanning
Ecosystem Integrations
- OpenAPI / Swagger generation
- GraphQL plugin
- Server-Sent Events support
- AWS Lambda adapter
- Database integration guides (Drizzle, Prisma)
Documentation
- API reference completion for all packages
- Cookbook with task-oriented recipes
- Starter templates and example repository
Framework Goals
- Performance — keep the benchmark harness honest and reproducible; document methodology when it changes (see Performance)
- Bundle size — keep core under 200KB memory footprint
- Type safety — full TypeScript strict mode, zero
any - Dual paradigm — functional routes and decorator-based controllers
- Zero runtime dependencies — except
reflect-metadatafor DI
Non-Goals
- Replacing Express or Fastify for every use case
- Building a full-stack framework (like Next.js)
- Supporting Node.js versions below 22
Feature Requests
- Vote on existing issues to signal priority
- Open a discussion to propose new ideas
- Contribute by picking up an unassigned item
Changelog
See the Changelog for release history.