chore(): resolve conflicts

Author: Tony133

.nvmrc

@@ -1 +1 @@
-16.16.0
+18.14.0

LICENSE

@@ -1,6 +1,6 @@
 (The MIT License)
 
-Copyright (c) 2017-2022 Kamil Myśliwiec <http://kamilmysliwiec.com>
+Copyright (c) 2017-2023 Kamil Myśliwiec <http://kamilmysliwiec.com>
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

content/cli/libraries.md

@@ -19,7 +19,7 @@ Any functionality that is suitable for re-use is a candidate for being managed a
 To get started with creating a library, run the following command:
 
 ```bash
-nest g library my-library
+$ nest g library my-library
 ```
 
 When you run the command, the `library` schematic prompts you for a prefix (AKA alias) for the library:
@@ -78,7 +78,7 @@ As with application-type projects, libraries each have their own `tsconfig.lib.j
 You can build the library with the CLI command:
 
 ```bash
-nest build my-library
+$ nest build my-library
 ```
 
 #### Using libraries

content/cli/workspaces.md

@@ -26,7 +26,7 @@ To enable monorepo mode, you start with a _standard mode_ structure, and add **p
 If we run:
 
 ```bash
-nest new my-project
+$ nest new my-project
 ```
 
 We've constructed a _standard mode_ structure, with a folder structure that looks like this:
@@ -49,8 +49,8 @@ We've constructed a _standard mode_ structure, with a folder structure that look
 We can convert this to a monorepo mode structure as follows:
 
 ```bash
-cd my-project
-nest generate app my-app
+$ cd my-project
+$ nest generate app my-app
 ```
 
 At this point, `nest` converts the existing structure to a **monorepo mode** structure. This results in a few important changes. The folder structure now looks like this:

content/controllers.md

@@ -268,6 +268,8 @@ getDocs(@Query('version') version) {
 
 Routes with static paths won't work when you need to accept **dynamic data** as part of the request (e.g., `GET /cats/1` to get cat with id `1`). In order to define routes with parameters, we can add route parameter **tokens** in the path of the route to capture the dynamic value at that position in the request URL. The route parameter token in the `@Get()` decorator example below demonstrates this usage. Route parameters declared in this way can be accessed using the `@Param()` decorator, which should be added to the method signature.
 
+> info **Hint** Routes with parameters should be declared after any static paths. This prevents the parameterized paths from intercepting traffic destined for the static paths.
+
 ```typescript
 @@filename()
 @Get(':id')

content/discover/who-uses.json

@@ -269,6 +269,8 @@
     "https://bewith.io",
     "https://swetrix.com",
     "https://swyftlogistics.com",
-    "https://evershop.io"
+    "https://evershop.io",
+    "https://e-design.ca",
+    "https://growthmill.com"
   ]
-}
+}

content/exception-filters.md

@@ -15,7 +15,7 @@ Out of the box, this action is performed by a built-in **global exception filter
 }
 ```
 
-> info **Hint** The global exception filter partially supports the `http-errors` library. Basically, any thrown exception containing the `statusCode` and `message` property will be properly populated and send back as a response (instead of the default `InternalServerErrorException` for unrecognized exceptions).
+> info **Hint** The global exception filter partially supports the `http-errors` library. Basically, any thrown exception containing the `statusCode` and `message` properties will be properly populated and sent back as a response (instead of the default `InternalServerErrorException` for unrecognized exceptions).
 
 #### Throwing standard exceptions
 
@@ -72,11 +72,11 @@ async findAll() {
     await this.service.findAll()
   } catch (error) { 
     throw new HttpException({
-    status: HttpStatus.FORBIDDEN,
-    error: 'This is a custom message',
-  }, HttpStatus.FORBIDDEN, {
-    cause: error
-  });
+      status: HttpStatus.FORBIDDEN,
+      error: 'This is a custom message',
+    }, HttpStatus.FORBIDDEN, {
+      cause: error
+    });
   }
 }
 ```
@@ -206,6 +206,8 @@ export class HttpExceptionFilter {
 
 > info **Hint** All exception filters should implement the generic `ExceptionFilter<T>` interface. This requires you to provide the `catch(exception: T, host: ArgumentsHost)` method with its indicated signature. `T` indicates the type of the exception.
 
+> warning **Warning** If you are using `@nestjs/platform-fastify` you can use `response.send()` instead of `response.json()`. Don't forget to import the correct types from `fastify`.
+
 The `@Catch(HttpException)` decorator binds the required metadata to the exception filter, telling Nest that this particular filter is looking for exceptions of type `HttpException` and nothing else. The `@Catch()` decorator may take a single parameter, or a comma-separated list. This lets you set up the filter for several types of exceptions at once.
 
 #### Arguments host
@@ -347,6 +349,8 @@ export class AllExceptionsFilter implements ExceptionFilter {
 }
 ```
 
+> warning **Warning** When combining an exception filter that catches everything with a filter that is bound to a specific type, the "Catch anything" filter should be declared first to allow the specific filter to correctly handle the bound type.
+
 #### Inheritance
 
 Typically, you'll create fully customized exception filters crafted to fulfill your application requirements. However, there might be use-cases when you would like to simply extend the built-in default **global exception filter**, and override the behavior based on certain factors.

content/faq/errors.md

@@ -10,6 +10,7 @@ Probably the most common error message is about Nest not being able to resolve d
 Nest can't resolve dependencies of the <provider> (?). Please make sure that the argument <unknown_token> at index [<index>] is available in the <module> context.
 
 Potential solutions:
+- Is <module> a valid NestJS module?
 - If <unknown_token> is a provider, is it part of the current <module>?
 - If <unknown_token> is exported from a separate @Module, is that module imported within <module>?
   @Module({
@@ -56,6 +57,7 @@ This likely happens when your project end up loading two Node modules of the pac
 Solutions:
 
 - For **Yarn** Workspaces, use the [nohoist feature](https://classic.yarnpkg.com/blog/2018/02/15/nohoist) to prevent hoisting the package `@nestjs/core`.
+- For **pnpm** Workspaces, set `@nestjs/core` as a peerDependencies in your other module and `"dependenciesMeta": {{ '{' }}"other-module-name": {{ '{' }}"injected": true{{ '}}' }}` in the app package.json where the module is imported. see: [dependenciesmetainjected](https://pnpm.io/package_json#dependenciesmetainjected)
 
 #### "Circular dependency" error
 

content/faq/raw-body.md

@@ -2,6 +2,8 @@
 
 One of the most common use-case for having access to the raw request body is performing webhook signature verifications. Usually to perform webhook signature validations the unserialized request body is required to calculate an HMAC hash.
 
+> warning **Warning** This feature can be used only if the built-in global body parser middleware is enabled, ie., you must not pass `bodyParser: false` when creating the app.
+
 #### Use with Express
 
 First enable the option when creating your Nest Express application:
@@ -35,7 +37,7 @@ First enable the option when creating your Nest Fastify application:
 ```typescript
 const app = await NestFactory.create<NestFastifyApplication>(
   AppModule,
-  new FastifyAdapter()
+  new FastifyAdapter(),
   {
     rawBody: true,
   }

content/faq/request-lifecycle.md

@@ -34,7 +34,7 @@ Interceptors, for the most part, follow the same pattern as guards, with one cat
 
 #### Pipes
 
-Pipes follow the standard global to controller to route bound sequence, with the same first in first out in regards to the `@usePipes()` parameters. However, at a route parameter level, if you have multiple pipes running, they will run in the order of the last parameter with a pipe to the first. This also applies to the route level and controller level pipes. For example, if we have the following controller:
+Pipes follow the standard global to controller to route bound sequence, with the same first in first out in regards to the `@UsePipes()` parameters. However, at a route parameter level, if you have multiple pipes running, they will run in the order of the last parameter with a pipe to the first. This also applies to the route level and controller level pipes. For example, if we have the following controller:
 
 ```typescript
 @UsePipes(GeneralValidationPipe)