Merge branch 'master' into master

Author: omermorad

.gitignore

@@ -6,6 +6,7 @@ dist/*
 !/dist/v5
 !/dist/v6
 !/dist/v7
+!/dist/v8
 
 /tmp
 /out-tsc

.husky/pre-commit

@@ -1,4 +1,4 @@
 #!/bin/sh
 . "$(dirname "$0")/_/husky.sh"
 
-npx lint-staged
+npx --no-install lint-staged

.nvmrc

@@ -1 +1 @@
-16.15.0
+16.16.0

content/cli/overview.md

@@ -93,5 +93,4 @@ See [usage](/cli/usages) for detailed descriptions for each command.
 | `build`    |       | Compiles an application or workspace into an output folder.                                           |
 | `start`    |       | Compiles and runs an application (or default project in a workspace).                                 |
 | `add`      |       | Imports a library that has been packaged as a **nest library**, running its install schematic.        |
-| `update`   | `u`   | Update `@nestjs` dependencies in the `package.json` `"dependencies"` list to their `@latest` version. |
 | `info`     | `i`   | Displays information about installed nest packages and other helpful system info.                     |

content/discover/who-uses.json

@@ -194,6 +194,10 @@
     {
       "logo": "/assets/logo/fuse-logo.svg",
       "url": "https://fuseautotech.com"
+    },
+    {
+      "logo": "/assets/logo/amplication.svg",
+      "url": "https://amplication.com"
     }
   ],
   "Body": [

content/faq/errors.md

@@ -17,17 +17,49 @@ Potential solutions:
   })
 ```
 
-The most common culprit of the error, is not having the `provider` in the module's `providers` array. Please make sure that the provider is indeed in the `providers` array and following [standard NestJS provider practices](/fundamentals/custom-providers#di-fundamentals).
+The most common culprit of the error, is not having the `<provider>` in the module's `providers` array. Please make sure that the provider is indeed in the `providers` array and following [standard NestJS provider practices](/fundamentals/custom-providers#di-fundamentals).
 
 There are a few gotchas, that are common. One is putting a provider in an `imports` array. If this is the case, the error will have the provider's name where `<module>` should be.
 
-If you run across this error while developing, take a look at the module mentioned in the error message and look at its `providers`. For each provider in the `providers` array, make sure the module has access to all of the dependencies. Often times, `providers` are duplicated in a "Feature Module" and a "Root Module" which means Nest will try to instantiate the provider twice. More than likely, the module containing the `provider` being duplicated should be added in the "Root Module"'s `imports` array instead.
+If you run across this error while developing, take a look at the module mentioned in the error message and look at its `providers`. For each provider in the `providers` array, make sure the module has access to all of the dependencies. Often times, `providers` are duplicated in a "Feature Module" and a "Root Module" which means Nest will try to instantiate the provider twice. More than likely, the module containing the `<provider>` being duplicated should be added in the "Root Module"'s `imports` array instead.
 
-If the `unknown_token` above is the string `dependency`, you might have a circular file import. This is different from the [circular dependency](./errors.md#circular-dependency-error) below because instead of having providers depend on each other in their constructors, it just means that two files end up importing each other. A common case would be a module file declaring a token and importing a provider, and the provider import the token constant from the module file. If you are using barrel files, ensure that your barrel imports do not end up creating these circular imports as well.
+If the `<unknown_token>` above is the string `dependency`, you might have a circular file import. This is different from the [circular dependency](/faq/common-errors#circular-dependency-error) below because instead of having providers depend on each other in their constructors, it just means that two files end up importing each other. A common case would be a module file declaring a token and importing a provider, and the provider import the token constant from the module file. If you are using barrel files, ensure that your barrel imports do not end up creating these circular imports as well.
+
+If the `<unknown_token>` above is the string `Object`, it means that you're injecting using an type/interface without a proper provider's token. To fix that, make sure you're importing the class reference or use a custom token with `@Inject()` decorator. Read the [custom providers page](/fundamentals/custom-providers).
+
+Also, make sure you didn't end up injecting the provider on itself because self-injections are not allowed in NestJS. When this happens, `<unknown_token>` will likely be equal to `<provider>`.
+
+If you are in a **monorepo setup**, you may face the same error as above but for core provider called `ModuleRef` as a `<unknown_token>`:
+
+```bash
+Nest can't resolve dependencies of the <provider> (?).
+Please make sure that the argument ModuleRef at index [<index>] is available in the <module> context.
+...
+```
+
+This likely happens when your project end up loading two Node modules of the package `@nestjs/core`, like this:
+
+```text
+.
+├── package.json
+├── apps
+│   └── api
+│       └── node_modules
+│           └── @nestjs/bull
+│               └── node_modules
+│                   └── @nestjs/core
+└── node_modules
+    ├── (other packages)
+    └── @nestjs/core
+```
+
+Solutions:
+
+- For **Yarn** Workspaces, use the [nohoist feature](https://classic.yarnpkg.com/blog/2018/02/15/nohoist) to prevent hoisting the package `@nestjs/core`.
 
 #### "Circular dependency" error
 
-Occasionally you'll find it difficult to avoid [circular dependencies](/fundamentals/circular-dependency) in your application. You'll need to take some steps to help Nest resolve these. Errors that arise from circular dependencies look like this:
+Occasionally you'll find it difficult to avoid [circular dependencies](https://docs.nestjs.com/fundamentals/circular-dependency) in your application. You'll need to take some steps to help Nest resolve these. Errors that arise from circular dependencies look like this:
 
 ```bash
 Nest cannot create the <module> instance.

content/faq/hybrid-application.md

@@ -27,7 +27,8 @@ const microserviceTcp = app.connectMicroservice<MicroserviceOptions>({
 const microserviceRedis = app.connectMicroservice<MicroserviceOptions>({
   transport: Transport.REDIS,
   options: {
-    url: 'redis://localhost:6379',
+    host: 'localhost',
+    port: 6379,
   },
 });
 
@@ -70,7 +71,10 @@ By default a hybrid application will not inherit global pipes, interceptors, gua
 To inherit these configuration properties from the main application, set the `inheritAppConfig` property in the second argument (an optional options object) of the `connectMicroservice()` call, as follow:
 
 ```typescript
-const microservice = app.connectMicroservice({
-  transport: Transport.TCP
-}, { inheritAppConfig: true });
+const microservice = app.connectMicroservice(
+  {
+    transport: Transport.TCP,
+  },
+  { inheritAppConfig: true },
+);
 ```

content/faq/raw-body.md

@@ -0,0 +1,59 @@
+### Raw body
+
+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.
+
+#### Use with Express
+
+First enable the option when creating your Nest Express application:
+
+```typescript
+const app = await NestFactory.create(AppModule, {
+  rawBody: true,
+});
+await app.listen(3000);
+```
+
+To access the raw request body in a controller, a convenience interface `RawBodyRequest` is provided to expose a `rawBody` field on the request: use the interface `RawBodyRequest` type:
+
+```typescript
+import { Controller, Post, RawBodyRequest, Req } from '@nestjs/common';
+import { Request } from 'express';
+
+@Controller('cats')
+class CatsController {
+  @Post()
+  create(@Req() req: RawBodyRequest<Request>) {
+    const raw = req.rawBody; // returns a `Buffer`.
+  }
+}
+```
+
+#### Use with Fastify
+
+First enable the option when creating your Nest Fastify application:
+
+```typescript
+const app = await NestFactory.create<NestFastifyApplication>(
+  AppModule,
+  new FastifyAdapter()
+  {
+    rawBody: true,
+  }
+);
+await app.listen(3000);
+```
+
+To access the raw request body in a controller, a convenience interface `RawBodyRequest` is provided to expose a `rawBody` field on the request: use the interface `RawBodyRequest` type:
+
+```typescript
+import { Controller, Post, RawBodyRequest, Req } from '@nestjs/common';
+import { FastifyRequest } from 'fastify';
+
+@Controller('cats')
+class CatsController {
+  @Post()
+  create(@Req() req: RawBodyRequest<FastifyRequest>) {
+    const raw = req.rawBody; // returns a `Buffer`.
+  }
+}
+```