You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/migration.md
+87Lines changed: 87 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,6 +201,93 @@ Additionally, the `ignoreEnvVars` configuration option, which previously allowed
201
201
202
202
A new `skipProcessEnv` option has also been introduced. This option allows you to prevent the `ConfigService#get` method from accessing the `process.env` object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.
203
203
204
+
#### Terminus module
205
+
206
+
If you are using the `TerminusModule` and have built your own custom health indicator, a new API has been introduced in version 11. The new `HealthIndicatorService` is designed to enhance the readability and testability of custom health indicators.
207
+
208
+
**Previous Approach**
209
+
210
+
Before version 11, a health indicator might have looked like this:
In version 11, it is recommended to use the new `HealthIndicatorService` API, which simplifies the implementation. Here's how the same health indicator can be implemented:
251
+
252
+
```typescript
253
+
@Injectable()
254
+
exportclassDogHealthIndicator {
255
+
constructor(
256
+
privatereadonlyhttpService:HttpService,
257
+
// Inject the `HealthIndicatorService` provided by the `TerminusModule`
- The `HealthIndicatorService` replaces the older `HealthIndicator` and `HealthCheckError` classes, providing a cleaner API for health checks.
287
+
- The `check` method allows easy state tracking (`up` or `down`) while supporting additional metadata to be included in health check responses.
288
+
289
+
> info **Info** Please note that the `HealthIndicator` and `HealthCheckError` classes have been marked as deprecated and are scheduled for removal in the next major release.
290
+
204
291
#### Node.js v16 no longer supported
205
292
206
293
Starting with NestJS 11, Node.js v16 is no longer supported, as it reached its end-of-life (EOL) on September 11, 2023. NestJS 11 now requires **Node.js v20 or higher**.
0 commit comments