npm / @nestjs/terminus
@nestjs/terminus
What changed in @nestjs/terminus 11 to 12, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-21.
13 breaking5 new APIs and options2 behavior and defaults3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@nestjs/terminus 1222 changes
Breaking changes 13
ConnectionNotFoundError is no longer exported.
The deprecated getStatus() method has been removed; use HealthIndicatorService.check(key).up(data) or .down(data).
Throwing inside a health indicator now causes an unexpected failure (500); only a returned down result marks the check unhealthy (503).
HealthCheckError is no longer exported.
The deprecated HealthIndicator base class has been removed; custom indicators should migrate to HealthIndicatorService.
MongoConnectionError is no longer exported.
The Mongoose health check pings the database instead of checking readyState.
The package is now ESM-only, so projects must use it as an ESM package.
The package requires Node ^20.19.0 || ^22.12.0 || >=24.0.0.
@nestjs/terminus no longer has runtime dependencies.
StorageExceededError is no longer exported.
TimeoutError is no longer exported.
UnhealthyResponseCodeError is no longer exported.
New APIs and options 4
Accepts a URL object in HttpHealthIndicator.pingCheck.
A new attempt() function is available.
Health indicators can now report a degraded status.
HealthCheckResult now includes responseTime.
Behavior and default changes 2
A dedicated HttpService is created instead of resolving HttpService from DI.
RMQ pingCheck no longer asserts a queue per probe.
Fixes and other changes 3
Fixes a memory leak in attempt().withTimeout() caused by AbortSignal.any().
shutting_down is set before awaiting the graceful shutdown timeout.
The microservice client is closed when the ping fails.
@nestjs/terminus 111 changes
New APIs and options 1
Custom loggers are provided through dependency injection.