NestJS v12.5.0
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.
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.
Review network binding and resource-limit settings, and test application startup for configurations now rejected as invalid.
- 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.
host: '0.0.0.0'# community_signal
How useful is this release to your stack?
Sign in with GitHub to cast your vote.
You’ll return to this release, then choose your vote.