Merge branch 'Fry98-sls-terser'

Author: kamilmysliwiec

content/faq/serverless.md

@@ -263,7 +263,7 @@ $ npx serverless offline
 Once the application is running, open your browser and navigate to `http://localhost:3000/dev/[ANY_ROUTE]` (where `[ANY_ROUTE]` is any endpoint registered in your application).
 
 In the sections above, we've shown that using `webpack` and bundling your app can have significant impact on the overall bootstrap time.
-However, to make it work with our example, there's one additional configuration you must add in your `webpack.config.js` file. Generally,
+However, to make it work with our example, there are a few additional configurations you must add in your `webpack.config.js` file. Generally,
 to make sure our `handler` function will be picked up, we must change the `output.libraryTarget` property to `commonjs2`.
 
 ```javascript
@@ -280,6 +280,31 @@ return {
 
 With this in place, you can now use `$ nest build --webpack` to compile your function's code (and then `$ npx serverless offline` to test it).
 
+It's also recommended (but **not required** as it will slow down your build process) to install the `terser-webpack-plugin` package and override its configuration to keep classnames intact when minifying your production build. Not doing so can result in incorrect behavior when using `class-validator` within your application.
+
+```javascript
+const TerserPlugin = require('terser-webpack-plugin');
+
+return {
+  ...options,
+  externals: [],
+  optimization: {
+    minimizer: [
+      new TerserPlugin({
+        terserOptions: {
+          keep_classnames: true,
+        },
+      }),
+    ],
+  },
+  output: {
+    ...options.output,
+    libraryTarget: 'commonjs2',
+  },
+  // ... the rest of the configuration
+};
+```
+
 #### Using standalone application feature
 
 Alternatively, if you want to keep your function very lightweight and you don't need any HTTP-related features (routing, but also guards, interceptors, pipes, etc.),

src/app/homepage/pages/microservices/custom-transport/custom-transport.component.html

@@ -197,8 +197,8 @@ <h4 appAnchor id="message-serialization"><span>Message serialization</span></h4>
 <p>If you need to add some custom logic around the serialization of responses on the client side, you can use a custom class that extends the <code>ClientProxy</code> class or one of its child classes. For modifying successful requests you can override the <code>serializeResponse</code> method, and for modifying any errors that go through this client you can override the <code>serializeError</code> method. To make use of this custom class, you can pass the class itself to the <code>ClientsModule.register()</code> method using the <code>customClass</code> property. Below is an example of a custom <code>ClientProxy</code> that serializes each error into an <code>RpcException</code>.</p>
 
 <span class="filename">
-  {{ 'error-handling.proxy' | extension: app36509a7a69ae46c59205b90a4a5155e70e440781.isJsActive }}
-<app-tabs #app36509a7a69ae46c59205b90a4a5155e70e440781></app-tabs>
+  {{ 'error-handling.proxy' | extension: app630c344fa86197723c3999961ed4f597aecb22ee.isJsActive }}
+<app-tabs #app630c344fa86197723c3999961ed4f597aecb22ee></app-tabs>
 </span><pre><code class="language-typescript">
 import &#123; ClientTcp, RpcException &#125; from &#39;@nestjs/microservices&#39;;
 
@@ -210,8 +210,8 @@ <h4 appAnchor id="message-serialization"><span>Message serialization</span></h4>
 </code></pre><p>and then use it in the <code>ClientsModule</code> like so:</p>
 
 <span class="filename">
-  {{ 'app.module' | extension: app830418197b35c62d70431550a1f060c5a80864fa.isJsActive }}
-<app-tabs #app830418197b35c62d70431550a1f060c5a80864fa></app-tabs>
+  {{ 'app.module' | extension: app8d31e231893684261e1aeae0662becdd6b838a8f.isJsActive }}
+<app-tabs #app8d31e231893684261e1aeae0662becdd6b838a8f></app-tabs>
 </span><pre><code class="language-typescript">
 @Module(&#123;
   imports: [