NestJS release notes, breaking changes, and upgrade notes.
A progressive Node.js framework for scalable server-side apps StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
This release consists primarily of fixes across `@nestjs/common` and `@nestjs/core`, including validation and logging behavior, HTTP routing and middleware matching, dependency injection, and streaming/SSE handling. It also changes invalid middleware targets to fail application startup; the supplied notes are truncated, so this summary covers only the visible entries.
affected
NestJS 11.2.10 users may see corrected behavior across validation, routing, middleware, dependency injection, logging, and streaming; applications with invalid middleware targets will now fail during startup.
action
Review middleware registrations to ensure every target is a controller or route, and upgrade to receive the listed fixes.
release_signals
-An invalid middleware target that is neither a controller nor a route now causes the application to fail at startup, rather than being accepted.
This release adds configurable limits for message sizes, buffering, pending work, and multipart requests across WebSocket, Socket.IO, TCP, gRPC, Redis, RabbitMQ, and Fastify. It also changes several defaults and runtime behaviors, including TCP binding to localhost when the host is empty, multipart part limits, streamed-response serialization, and earlier startup validation; the supplied notes end mid-section, so additional changes may be omitted.
affected
Applications using TCP, WebSocket, Socket.IO, multipart uploads, or startup-validated providers and middleware may need configuration or code changes to accommodate the new defaults and validation.
action
Review network binding and resource-limit settings, and test application startup for configurations now rejected as invalid.
release_signals
-TCP servers now bind to localhost when `host` is empty or unset; configure `host: '0.0.0.0'` or `'::'` to listen on every interface.
This release is a broad bug-fix update across NestJS common, core, and related integrations. It improves validation and request handling, middleware routing and enhancer behavior, and stream/SSE error handling, including safeguards that prevent internal error messages from being exposed in responses.
affected
NestJS v11 applications using validation pipes, middleware, global enhancers, file streams, SSE, or HTTP error handling may see corrected behavior; apps with request-scoped class global enhancers may encounter a startup failure.
action
Upgrade to v11.2.8 and verify startup for applications that register global enhancers with request-scoped dependencies.
release_signals
-Request-scoped class-based global enhancers, such as an `APP_GUARD` registered with `useClass`, now fail at startup rather than running without their dependencies.
This release introduces new configuration options for event streaming, WebSocket adapters, and validation pipes, along with several behavior changes and bug fixes. Notable changes include deprecation warnings for certain microservice patterns and updates to middleware exclusion behavior.
affected
Developers using `@EventPattern()` handlers with `ClientProxy#send()` on certain microservices will see deprecation warnings and need to prepare for future breaking changes.
action
Review deprecation warnings for `@EventPattern()` handlers and update middleware exclusions if using `MiddlewareConsumer.exclude()`.
release_signals
-Deprecation warning for `@EventPattern()` handlers that reply to `ClientProxy#send()` on TCP, Redis, NATS, MQTT, and RabbitMQ. In the next major version, event handlers will not reply to `send()`.
NestJS v12 introduces ESM-ready packages, Standard Schema support, a rebuilt CLI, and native observability. It requires Node.js v20.19+ or v22.12+ and includes several breaking changes.
affected
All NestJS users upgrading from v11 to v12 are affected, particularly those using custom bootstrapping, bundler configurations, or older Node.js versions.
action
Follow the migration guide and use `nest upgrade` to automate parts of the upgrade process.
release_signals
-Packages now ship as ESM. While CommonJS applications continue to work via `require(esm)`, custom bootstrapping, bundler, and test-runner configurations may need review.
-Several resource limits have lower or newly enforced defaults: WebSocket `maxPayload` is 1 MB instead of 100 MB, TCP `maxBufferSize` is 16 Mi characters instead of 128 Mi, and multipart requests default to at most 1000 parts.
-An upload route option set to `undefined` or `null` now retains the module's value; use `Infinity` to lift a limit.
-Some invalid configurations that previously could run now fail at startup, including invalid middleware routes and guards, interceptors, or pipes that cannot run.
!New default limits constrain message sizes, queued or pending work, wildcard channel length, and multipart request size; these changes can reduce resource-exhaustion exposure.
+Adds configurable message and queue limits across WebSocket, Socket.IO, TCP, gRPC, Redis, RabbitMQ, and Fastify multipart handling.
+Adds per-object serialization for streamed HTTP responses, applying serializer exclusions, groups, and schemas to each NDJSON line.
+Adds SSE keepalive comments every five seconds while a client socket is paused.
migration_steps2 steps
01If a TCP server must listen on all interfaces, set `host: '0.0.0.0'` or `host: '::'`.
02Review workloads against the new message, buffer, and multipart defaults; raise the relevant limits where needed, or use `0` or `Infinity` where the release notes specify that this lifts a limit.
-Global enhancers that are not instantiated now fail at startup instead of being silently skipped.
!Redacts messages from unexposed HTTP errors and SSE error events, and prevents `StreamableFile` or SSE errors from exposing internal error messages.
+Makes the SSE pending-data limit configurable.
migration_steps1 steps
01Review request-scoped class-based global enhancers (for example, `APP_GUARD` with `useClass`): the application now fails at startup if such an enhancer is registered.
!`@EventPattern()` handlers that reply to `ClientProxy#send()` on TCP, Redis, NATS, MQTT, and RabbitMQ are now deprecated and will log a warning.
+`@Sse({ maxPendingDataLength })` to limit event data waiting for a client.
+`IoAdapter` and `WsAdapter` now support `maxConcurrentMessages` to limit messages handled at once.
+`ValidationPipe` now has `maxErrorMessagesLength` to limit validation error messages.
+Kafka `parser.maxMessageSize` to limit message size after decompression.
+TCP server `drainTimeout` to disconnect peers with unread responses.
migration_steps1 steps
01Update `@nestjs/core` together with `@nestjs/platform-express` or `@nestjs/platform-fastify` to ensure middleware exclusions work correctly with router matching options.