Merge branch 'nestjs:master' into cookieMonsterDev/prisma-recipe

Author: cookieMonsterDev

content/discover/who-uses.json

@@ -180,6 +180,7 @@
     "https://devitjobs.com",
     "https://formation.tech",
     "https://gofirmex.com",
-    "https://vbdhub.org"
+    "https://vbdhub.org",
+    "https://www.arven-tech.com"
   ]
 }

content/graphql/quick-start.md

@@ -12,10 +12,10 @@ Start by installing the required packages:
 
 ```bash
 # For Express and Apollo (default)
-$ npm i @nestjs/graphql @nestjs/apollo @apollo/server graphql
+$ npm i @nestjs/graphql @nestjs/apollo @apollo/server@^4.12.2 graphql
 
 # For Fastify and Apollo
-# npm i @nestjs/graphql @nestjs/apollo @apollo/server @as-integrations/fastify graphql
+# npm i @nestjs/graphql @nestjs/apollo @apollo/server@^4.12.2 @as-integrations/fastify graphql
 
 # For Fastify and Mercurius
 # npm i @nestjs/graphql @nestjs/mercurius graphql mercurius

content/microservices/kafka.md

@@ -171,7 +171,7 @@ client: ClientKafkaProxy;
 
 #### Message pattern
 
-The Kafka microservice message pattern utilizes two topics for the request and reply channels. The `ClientKafkaProxy#send()` method sends messages with a [return address](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ReturnAddress.html) by associating a [correlation id](https://www.enterpriseintegrationpatterns.com/patterns/messaging/CorrelationIdentifier.html), reply topic, and reply partition with the request message. This requires the `ClientKafkaProxy` instance to be subscribed to the reply topic and assigned to at least one partition before sending a message.
+The Kafka microservice message pattern utilizes two topics for the request and reply channels. The `ClientKafkaProxy.send()` method sends messages with a [return address](https://www.enterpriseintegrationpatterns.com/patterns/messaging/ReturnAddress.html) by associating a [correlation id](https://www.enterpriseintegrationpatterns.com/patterns/messaging/CorrelationIdentifier.html), reply topic, and reply partition with the request message. This requires the `ClientKafkaProxy` instance to be subscribed to the reply topic and assigned to at least one partition before sending a message.
 
 Subsequently, you need to have at least one reply topic partition for every Nest application running. For example, if you are running 4 Nest applications but the reply topic only has 3 partitions, then 1 of the Nest applications will error out when trying to send a message.
 
@@ -183,7 +183,7 @@ To prevent the `ClientKafkaProxy` consumers from losing response messages, a Nes
 
 #### Message response subscription
 
-> warning **Note** This section is only relevant if you use [request-response](/microservices/basics#request-response) message style (with the `@MessagePattern` decorator and the `ClientKafkaProxy#send` method). Subscribing to the response topic is not necessary for the [event-based](/microservices/basics#event-based) communication (`@EventPattern` decorator and `ClientKafkaProxy#emit` method).
+> warning **Note** This section is only relevant if you use [request-response](/microservices/basics#request-response) message style (with the `@MessagePattern` decorator and the `ClientKafkaProxy.send` method). Subscribing to the response topic is not necessary for the [event-based](/microservices/basics#event-based) communication (`@EventPattern` decorator and `ClientKafkaProxy.emit` method).
 
 The `ClientKafkaProxy` class provides the `subscribeToResponseOf()` method. The `subscribeToResponseOf()` method takes a request's topic name as an argument and adds the derived reply topic name to a collection of reply topics. This method is required when implementing the message pattern.
 

content/recipes/cqrs.md

@@ -89,7 +89,9 @@ export class KillDragonCommand extends Command<{
   constructor(
     public readonly heroId: string,
     public readonly dragonId: string,
-  ) {}
+  ) {
+    super();
+  }
 }
 @@switch
 export class KillDragonCommand extends Command {

content/recipes/terminus.md

@@ -2,7 +2,7 @@
 
 Terminus integration provides you with **readiness/liveness** health checks. Healthchecks are crucial when it comes to complex
 backend setups. In a nutshell, a health check in the realm of web development usually consists of a special address, for example, `https://my-website.com/health/readiness`.
-A service or a component of your infrastructure (e.g., [Kubernetes](https://kubernetes.io/) checks this address continuously. Depending on the HTTP status code returned from a `GET` request to this address the service will take action when it receives an "unhealthy" response.
+A service or a component of your infrastructure (e.g., [Kubernetes](https://kubernetes.io/) checks this address continuously). Depending on the HTTP status code returned from a `GET` request to this address the service will take action when it receives an "unhealthy" response.
 Since the definition of "healthy" or "unhealthy" varies with the type of service you provide, the **Terminus** integration supports you with a
 set of **health indicators**.
 

content/security/authorization.md

@@ -220,7 +220,7 @@ export enum Action {
 }
 ```
 
-> warning **Notice** `manage` is a special keyword in CASL which represents "any" action.
+> warning **Notice** `manage` is a special keyword in CASL which represents "any action".
 
 To encapsulate CASL library, let's generate the `CaslModule` and `CaslAbilityFactory` now.
 

content/techniques/caching.md

@@ -38,7 +38,7 @@ To interact with the cache manager instance, inject it to your class using the `
 constructor(@Inject(CACHE_MANAGER) private cacheManager: Cache) {}
 ```
 
-> info **Hint** The `Cache` class is imported from the `cache-manager`, while `CACHE_MANAGER` token from the `@nestjs/cache-manager` package.
+> info **Hint** The `Cache` class and the `CACHE_MANAGER` token are both imported from the `@nestjs/cache-manager` package.
 
 The `get` method on the `Cache` instance (from the `cache-manager` package) is used to retrieve items from the cache. If the item does not exist in the cache, `null` will be returned.
 
@@ -236,7 +236,7 @@ With this in place, you can register the `CacheModule` with multiple stores as s
 import { Module } from '@nestjs/common';
 import { CacheModule } from '@nestjs/cache-manager';
 import { AppController } from './app.controller';
-import { createKeyv } from '@keyv/redis';
+import KeyvRedis from '@keyv/redis';
 import { Keyv } from 'keyv';
 import { CacheableMemory } from 'cacheable';
 
@@ -249,7 +249,7 @@ import { CacheableMemory } from 'cacheable';
             new Keyv({
               store: new CacheableMemory({ ttl: 60000, lruSize: 5000 }),
             }),
-            createKeyv('redis://localhost:6379'),
+            new KeyvRedis('redis://localhost:6379'),
           ],
         };
       },

content/techniques/compression.md

@@ -33,9 +33,15 @@ $ npm i --save @fastify/compress
 
 Once the installation is complete, apply the `@fastify/compress` middleware as global middleware.
 
+> warning **Warning** Please ensure, that you use the type `NestFastifyApplication` when creating the application. Otherwise, you cannot use `register` to apply the compression-middleware.
+
 ```typescript
+import { FastifyAdapter, NestFastifyApplication } from '@nestjs/platform-fastify';
+
 import compression from '@fastify/compress';
-// somewhere in your initialization file
+
+// inside bootstrap()
+const app = await NestFactory.create<NestFastifyApplication>(AppModule, new FastifyAdapter());
 await app.register(compression);
 ```
 

content/techniques/queues.md

@@ -230,7 +230,7 @@ export class AudioConsumer extends WorkerHost {
 
 The process method is called whenever the worker is idle and there are jobs to process in the queue. This handler method receives the `job` object as its only argument. The value returned by the handler method is stored in the job object and can be accessed later on, for example in a listener for the completed event.
 
-`Job` objects have multiple methods that allow you to interact with their state. For example, the above code uses the `progress()` method to update the job's progress. See [here](https://api.docs.bullmq.io/classes/v4.Job.html) for the complete `Job` object API reference.
+`Job` objects have multiple methods that allow you to interact with their state. For example, the above code uses the `updateProgress()` method to update the job's progress. See [here](https://api.docs.bullmq.io/classes/v4.Job.html) for the complete `Job` object API reference.
 
 In the older version, Bull, you could designate that a job handler method will handle **only** jobs of a certain type (jobs with a specific `name`) by passing that `name` to the `@Process()` decorator as shown below.
 

content/techniques/sql.md

@@ -113,7 +113,7 @@ export class User {
 }
 ```
 
-> info **Hint** Learn more about entities in the [TypeORM documentation](https://typeorm.io/#/entities).
+> info **Hint** Learn more about entities in the [TypeORM documentation](https://typeorm.io/docs/entity/entities/).
 
 The `User` entity file sits in the `users` directory. This directory contains all files related to the `UsersModule`. You can decide where to keep your model files, however, we recommend creating them near their **domain**, in the corresponding module directory.