chore(): update branch with the master

Author: Tony133

.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/cli/usages.md

@@ -34,6 +34,7 @@ Creates and initializes a new Nest project. Prompts for package manager.
 | `--package-manager [package-manager]` | Specify package manager. Use `npm`, `yarn`, or `pnpm`. Package manager must be installed globally.<br/> Alias: `-p` |
 | `--language [language]`               | Specify programming language (`TS` or `JS`).<br/> Alias: `-l`                                                       |
 | `--collection [collectionName]`       | Specify schematics collection. Use package name of installed npm package containing schematic.<br/> Alias: `-c`     |
+| `--strict`                            | Start the project with the following TypeScript compiler flags enabled: `strictNullChecks`, `noImplicitAny`, `strictBindCallApply`, `forceConsistentCasingInFileNames`, `noFallthroughCasesInSwitch` |
 
 #### nest generate
 
@@ -63,8 +64,8 @@ $ nest g <schematic> <name> [options]
 | `filter`      | `f`   | Generate a filter declaration.                                                                               |
 | `gateway`     | `ga`  | Generate a gateway declaration.                                                                              |
 | `guard`       | `gu`  | Generate a guard declaration.                                                                                |
-| `interface`   |       | Generate an interface.                                                                                       |
-| `interceptor` | `in`  | Generate an interceptor declaration.                                                                         |
+| `interface`   | `itf` | Generate an interface.                                                                                       |
+| `interceptor` | `itc` | Generate an interceptor declaration.                                                                         |
 | `middleware`  | `mi`  | Generate a middleware declaration.                                                                           |
 | `module`      | `mo`  | Generate a module declaration.                                                                               |
 | `pipe`        | `pi`  | Generate a pipe declaration.                                                                                 |
@@ -88,6 +89,12 @@ $ nest g <schematic> <name> [options]
 
 Compiles an application or workspace into an output folder.
 
+Also, the `build` command is responsible for:
+
+- mapping paths (if using path aliases) via `tsconfig-paths`
+- annotating DTOs with OpenAPI decorators (if `@nestjs/swagger` CLI plugin is enabled)
+- annotating DTOs with GraphQL decorators (if `@nestjs/graphql` CLI plugin is enabled)
+
 ```bash
 $ nest build <name> [options]
 ```
@@ -152,17 +159,6 @@ $ nest add <name> [options]
 | -------- | ---------------------------------- |
 | `<name>` | The name of the library to import. |
 
-#### nest update
-
-Updates `@nestjs` dependencies in the `package.json` `"dependencies"` list to their `@latest` version.
-
-##### Options
-
-| Option    | Description                                                             |
-| --------- | ----------------------------------------------------------------------- |
-| `--force` | Do **upgrade** instead of update <br/>Alias `-f`                        |
-| `--tag`   | Update to tagged version (use `@latest`, `@<tag>`, etc) <br/>Alias `-t` |
-
 #### nest info
 
 Displays information about installed nest packages and other helpful system info. For example:

content/cli/workspaces.md

@@ -197,8 +197,9 @@ These properties specify the compiler to use as well as various options that aff
 These properties specify the default generate options to be used by the `nest generate` command.
 
 | Property Name | Property Value Type | Description                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| ------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|---------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `spec`        | boolean _or_ object | If the value is boolean, a value of `true` enables `spec` generation by default and a value of `false` disables it. A flag passed on the CLI command line overrides this setting, as does a project-specific `generateOptions` setting (more below). If the value is an object, each key represents a schematic name, and the boolean value determines whether the default spec generation is enabled / disabled for that specific schematic. |
+| `flat`        | boolean             | If true, all generate commands will generate a flat structure                                                                                                                                                                                                                                                                                                                                                                                 |
 
 The following example uses a boolean value to specify that spec file generation should be disabled by default for all projects:
 
@@ -211,6 +212,17 @@ The following example uses a boolean value to specify that spec file generation
 }
 ```
 
+The following example uses a boolean value to specify flat file generation should be the default for all projects:
+
+```javascript
+{
+  "generateOptions": {
+    "flat": true
+  },
+  ...
+}
+```
+
 In the following example, `spec` file generation is disabled only for `service` schematics (e.g., `nest generate service...`):
 
 ```javascript

content/discover/who-uses.json

@@ -190,6 +190,14 @@
     {
       "logo": "/assets/logo/vue-storefront.png",
       "url": "https://www.vuestorefront.io/"
+    },
+    {
+      "logo": "/assets/logo/fuse-logo.svg",
+      "url": "https://fuseautotech.com"
+    },
+    {
+      "logo": "/assets/logo/amplication.svg",
+      "url": "https://amplication.com"
     }
   ],
   "Body": [
@@ -258,6 +266,9 @@
     "https://dyrector.io",
     "https://stijlbreuk.nl",
     "https://polygon-software.ch",
-    "https://bewith.io"
+    "https://bewith.io",
+    "https://swetrix.com",
+    "https://swyftlogistics.com",
+    "https://evershop.io"
   ]
-}
+}

content/exception-filters.md

@@ -60,16 +60,24 @@ in the `response` argument. To override the entire JSON response body, pass an o
 The second constructor argument - `status` - should be a valid HTTP status code.
 Best practice is to use the `HttpStatus` enum imported from `@nestjs/common`.
 
-Here's an example overriding the entire response body:
+There is a **third** constructor argument (optional) - `options` - that can be used to provide an error [cause](https://nodejs.org/en/blog/release/v16.9.0/#error-cause). This `cause` object is not serialized into the response object, but it can be useful for logging purposes, providing valuable information about the inner error that caused the `HttpException` to be thrown.
+
+Here's an example overriding the entire response body and providing an error cause:
 
 ```typescript
 @@filename(cats.controller)
 @Get()
 async findAll() {
-  throw new HttpException({
+  try {
+    await this.service.findAll()
+  } catch (error) { 
+    throw new HttpException({
     status: HttpStatus.FORBIDDEN,
     error: 'This is a custom message',
-  }, HttpStatus.FORBIDDEN);
+  }, HttpStatus.FORBIDDEN, {
+    cause: error
+  });
+  }
 }
 ```
 
@@ -130,6 +138,22 @@ Nest provides a set of standard exceptions that inherit from the base `HttpExcep
 - `GatewayTimeoutException`
 - `PreconditionFailedException`
 
+All the built-in exceptions can also provide both an error `cause` and an error description using the `options` parameter:
+
+```typescript
+throw new BadRequestException('Something bad happened', { cause: new Error(), description: 'Some error description' })
+```
+
+Using the above, this is how the response would look:
+
+```json
+{
+  "message": "Something bad happened",
+  "error": "Some error description",
+  "statusCode": 400,
+}
+```
+
 #### Exception filters
 
 While the base (built-in) exception filter can automatically handle many cases for you, you may want **full control** over the exceptions layer. For example, you may want to add logging or use a different JSON schema based on some dynamic factors. **Exception filters** are designed for exactly this purpose. They let you control the exact flow of control and the content of the response sent back to the client.

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 },
+);
 ```