Merge branch 'master' of https://github.com/nestjs/docs.nestjs.com

Author: kamilmysliwiec

content/devtools/overview.md

@@ -70,7 +70,7 @@ First, open up the `main.ts` file and update the `bootstrap()` call, as follows:
 
 ```typescript
 bootstrap().catch((err) => {
-  writeFileSync('graph.json', PartialGraphHost.toString() ?? '');
+  fs.writeFileSync('graph.json', PartialGraphHost.toString() ?? '');
   process.exit(1);
 });
 ```
@@ -130,7 +130,7 @@ To save a serialized graph to a file, use the following code:
 
 ```typescript
 await app.listen(3000); // OR await app.init()
-writeFileSync('./graph.json', app.get(SerializedGraph).toString());
+fs.writeFileSync('./graph.json', app.get(SerializedGraph).toString());
 ```
 
 > info **Hint** `SerializedGraph` is exported from the `@nestjs/core` package.

content/faq/errors.md

@@ -4,6 +4,8 @@ During your development with NestJS, you may encounter various errors as you lea
 
 #### "Cannot resolve dependency" error
 
+> info **Hint** Check out the [NestJS Devtools](/devtools/overview#investigating-the-cannot-resolve-dependency-error) which can help you resolve the "Cannot resolve dependency" error effortlessly.
+
 Probably the most common error message is about Nest not being able to resolve dependencies of a provider. The error message usually looks something like this:
 
 ```bash
@@ -20,8 +22,6 @@ 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).
 
-<app-banner-devtools></app-banner-devtools>
-
 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.
@@ -32,6 +32,8 @@ If the `<unknown_token>` above is the string `Object`, it means that you're inje
 
 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>`.
 
+<app-banner-devtools></app-banner-devtools>
+
 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

content/faq/global-prefix.md

@@ -20,3 +20,5 @@ Alternatively, you can specify route as a string (it will apply to every request
 ```typescript
 app.setGlobalPrefix('v1', { exclude: ['cats'] });
 ```
+
+> info **Hint** The `path` property supports wildcard parameters using the [path-to-regexp](https://github.com/pillarjs/path-to-regexp#parameters) package. Note: this does not accept wildcard asterisks `*`. Instead, you must use parameters (e.g., `(.*)`, `:splat*`).

content/faq/hybrid-application.md

@@ -4,7 +4,7 @@ A hybrid application is one that both listens for HTTP requests, as well as make
 
 ```typescript
 const app = await NestFactory.create(AppModule);
-const microservice = app.connectMicroservice({
+const microservice = app.connectMicroservice<MicroserviceOptions>({
   transport: Transport.TCP,
 });
 
@@ -71,7 +71,7 @@ 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(
+const microservice = app.connectMicroservice<MicroserviceOptions>(
   {
     transport: Transport.TCP,
   },

content/microservices/basics.md

@@ -38,7 +38,7 @@ async function bootstrap() {
 bootstrap();
 @@switch
 import { NestFactory } from '@nestjs/core';
-import { Transport, MicroserviceOptions } from '@nestjs/microservices';
+import { Transport } from '@nestjs/microservices';
 import { AppModule } from './app.module';
 
 async function bootstrap() {

content/microservices/kafka.md

@@ -371,7 +371,7 @@ The Kafka microservice components append a description of their respective role
 
 ```typescript
 @@filename(main)
-const app = await NestFactory.createMicroservice(AppModule, {
+const app = await NestFactory.createMicroservice<MicroserviceOptions>(AppModule, {
   transport: Transport.KAFKA,
   options: {
     client: {

content/microservices/nats.md

@@ -77,7 +77,7 @@ NATS provides a built-in load balancing feature called [distributed queues](http
 
 ```typescript
 @@filename(main)
-const app = await NestFactory.createMicroservice(AppModule, {
+const app = await NestFactory.createMicroservice<MicroserviceOptions>(AppModule, {
   transport: Transport.NATS,
   options: {
     servers: ['nats://localhost:4222'],

content/recipes/automock.md

@@ -71,6 +71,11 @@ describe('CatsService unit spec', () => {
   beforeAll(() => {
     const { unit, unitRef } = TestBed.create(CatsService)
       .mock(HttpService)
+      .use({ get: jest.fn() })
+      .mock(Logger)
+      .use({ log: jest.fn() })
+      .mock(CatsDal)
+      .use({ saveCats: jest.fn() })
       .compile();
 
     underTest = unit;
@@ -82,7 +87,7 @@ describe('CatsService unit spec', () => {
 
   describe('when getting all the cats', () => {
     test('then meet some expectations', async () => {
-      httpService.mockResolvedValueOnce([{ id: 1, name: 'Catty' }]);
+      httpService.get.mockResolvedValueOnce([{ id: 1, name: 'Catty' }]);
       await catsService.getAllCats();
 
       expect(logger.log).toBeCalled();

content/techniques/queues.md

@@ -241,6 +241,8 @@ You can designate that a job handler method will handle **only** jobs of a certa
 async transcode(job: Job<unknown>) { ... }
 ```
 
+> warning **Warning** When defining multiple consumers for the same queue, the `concurrency` option in `@Process({ concurrency: 1 })` won't take effect. The minimum `concurrency` will match the number of consumers defined. This also applies even if `@Process()` handlers use a different `name` to handle named jobs.
+
 #### Request-scoped consumers
 
 When a consumer is flagged as request-scoped (learn more about the injection scopes [here](/fundamentals/injection-scopes#provider-scope)), a new instance of the class will be created exclusively for each job. The instance will be garbage-collected after the job has completed.