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

Author: kamilmysliwiec

.nvmrc

@@ -1 +1 @@
-12.19.0
+12.19.1

content/middlewares.md

@@ -194,8 +194,6 @@ consumer
 
 With the example above, `LoggerMiddleware` will be bound to all routes defined inside `CatsController` **except** the three passed to the `exclude()` method.
 
-<app-banner-shop></app-banner-shop>
-
 #### Functional middleware
 
 The `LoggerMiddleware` class we've been using is quite simple. It has no members, no additional methods, and no dependencies. Why can't we just define it in a simple function instead of a class? In fact, we can. This type of middleware is called **functional middleware**. Let's transform the logger middleware from class-based into functional middleware to illustrate the difference:

content/techniques/validation.md

@@ -16,7 +16,7 @@ In the [Pipes](/pipes) chapter, we went through the process of building simple p
 
 #### Using the built-in ValidationPipe
 
-> info **Hint** The `ValidationPipe` is imported from the `@nestjs/common` package.
+> info **Hint** The `ValidationPipe` is exported from the `@nestjs/common` package.
 
 Because this pipe uses the `class-validator` and `class-transformer` libraries, there are many options available. You configure these settings via a configuration object passed to the pipe. Following are the built-in options:
 

lighthouserc.json

@@ -11,7 +11,7 @@
         ],
         "categories:performance": [
           "error",
-          { "minScore": 0.4, "aggregationMethod": "optimistic" }
+          { "minScore": 0.35, "aggregationMethod": "optimistic" }
         ],
         "categories:best-practices": [
           "error",