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

Author: kamilmysliwiec

content/discover/who-uses.json

@@ -161,6 +161,16 @@
       "logo": "/assets/logo/facile.png",
       "url": "https://www.facile.it",
       "width": "100px"
+    },
+    {
+      "logo": "/assets/logo/interfacewerk.png",
+      "url": "https://interfacewerk.de",
+      "width": "130px"
+    },
+    {
+      "logo": "/assets/logo/ottonova.png",
+      "url": "https://www.ottonova.de",
+      "width": "130px"
     }
   ],
   "Body": [
@@ -207,6 +217,7 @@
     "https://harmonize.health",
     "https://accerlery.be",
     "https://www.facile.it",
-    "https://shopback.com"
+    "https://shopback.com",
+    "https://www.ottonova.de"
   ]
 }

content/faq/request-lifecycle.md

@@ -4,7 +4,7 @@ Nest applications handle requests and produce responses in a sequence we refer t
 
 #### Middleware
 
-Middleware is executed in a particular sequence. First, Nest runs globally bound middleware (such as middleware bound with `app.use`) and then it runs [module bound middleware](/middleware), which are determined on paths. Middleware are run sequentially in the order they are bound, similar to the way middleware in Express works.
+Middleware is executed in a particular sequence. First, Nest runs globally bound middleware (such as middleware bound with `app.use`) and then it runs [module bound middleware](/middleware), which are determined on paths. Middleware are run sequentially in the order they are bound, similar to the way middleware in Express works. In the case of middleware bound across different modules, the middleware bound to the root module will run first, and then middleware will run in the order that the modules are added to the imports array.
 
 #### Guards
 

content/fundamentals/lifecycle-events.md

@@ -22,7 +22,7 @@ In the following table, `onModuleDestroy`, `beforeApplicationShutdown` and `onAp
 | `beforeApplicationShutdown()`\* | Called after all `onModuleDestroy()` handlers have completed (Promises resolved or rejected);<br />once complete (Promises resolved or rejected), all existing connections will be closed (`app.close()` called). |
 | `onApplicationShutdown()`\*     | Called after connections close (`app.close()` resolves.                                                                                                                                                           |
 
-\* For these events, if you're not calling `app.close()` explicitly, you must opt-in to make them work with system signals such as `SIGTERM`. See [Application shutdown](#application-shutdown) below.
+\* For these events, if you're not calling `app.close()` explicitly, you must opt-in to make them work with system signals such as `SIGTERM`. See [Application shutdown](fundamentals/lifecycle-events#application-shutdown) below.
 
 > warning **Warning** The lifecycle hooks listed above are not triggered for **request-scoped** classes. Request-scoped classes are not tied to the application lifecycle and their lifespan is unpredictable. They are exclusively created for each request and automatically garbage-collected after the response is sent.
 

content/graphql/quick-start.md

@@ -101,6 +101,15 @@ GraphQLModule.forRoot({
 }),
 ```
 
+By default, the types in the generated schema will be in the order they are defined in the included modules. To sort the schema lexicographically, set the `sortSchema` property to `true`:
+
+```typescript
+GraphQLModule.forRoot({
+  autoSchemaFile: join(process.cwd(), 'src/schema.gql'),
+  sortSchema: true,
+}),
+```
+
 A fully working code first sample is available [here](https://github.com/nestjs/nest/tree/master/sample/23-graphql-code-first).
 
 #### Schema first

content/recipes/hot-reload.md

@@ -32,7 +32,7 @@ module.exports = function(options) {
     watch: true,
     externals: [
       nodeExternals({
-        whitelist: ['webpack/hot/poll?100'],
+        allowlist: ['webpack/hot/poll?100'],
       }),
     ],
     plugins: [
@@ -106,7 +106,7 @@ module.exports = {
   target: 'node',
   externals: [
     nodeExternals({
-      whitelist: ['webpack/hot/poll?100'],
+      allowlist: ['webpack/hot/poll?100'],
     }),
   ],
   module: {

content/techniques/logger.md

@@ -135,6 +135,8 @@ Here we use the `get()` method on the `NestApplication` instance to retrieve the
 
 You can also inject this `MyLogger` provider in your feature classes, thus ensuring consistent logging behavior across both Nest system logging and application logging. See <a href="techniques/logger#using-the-logger-for-application-logging">Using the logger for application logging</a> below for more information.
 
+The only downside of this solution is that your first initialization messages won't be handled by your logger instance, though, it shouldn't really matter at this point.
+
 #### Using the logger for application logging
 
 We can combine several of the techniques above to provide consistent behavior and formatting across both Nest system logging and our own application event/message logging. In this section, we'll achieve this with the following steps: