@@ -230,7 +230,7 @@ const path = require('path');
230230module .exports = {
231231 // ...
232232 output: {
233- libraryTarget: ' commonjs2 ' ,
233+ libraryTarget: ' commonjs ' ,
234234 path: path .resolve (__dirname , ' .webpack' ),
235235 filename: ' [name].js' ,
236236 },
@@ -305,17 +305,17 @@ custom:
305305# ### Runtime dependencies
306306
307307If a runtime dependency is detected that is found in the `devDependencies` section and
308- so would not be packaged, the plugin will error until you explicitly exclude it (see `forceExclude` below)
308+ so would not be packaged, the plugin will error until you explicitly exclude it (see `forceExclude` below)
309309or move it to the `dependencies` section.
310310
311311# ### AWS-SDK
312312
313313An exception for the runtime dependency error is the AWS-SDK. All projects using the AWS-SDK normally
314- have it listed in `devDependencies` because AWS provides it already in their Lambda environment. In this case
314+ have it listed in `devDependencies` because AWS provides it already in their Lambda environment. In this case
315315the aws-sdk is automatically excluded and only an informational message is printed (in `--verbose` mode).
316316
317317The main reason for the warning is, that silently ignoring anything contradicts the declarative nature
318- of Serverless' service definition. So the correct way to define the handling for the aws-sdk is, as
318+ of Serverless' service definition. So the correct way to define the handling for the aws-sdk is, as
319319you would do for all other excluded modules (see `forceExclude` below).
320320
321321` ` ` yaml
@@ -342,7 +342,7 @@ custom:
342342` ` `
343343
344344You should select the packager, that you use to develop your projects, because only
345- then locked versions will be handled correctly, i.e. the plugin uses the generated
345+ then locked versions will be handled correctly, i.e. the plugin uses the generated
346346(and usually committed) package lock file that is created by your favorite packager.
347347
348348Each packager might support specific options that can be set in the `packagerOptions`
@@ -375,7 +375,7 @@ You can specify custom scripts that are executed after the installation of the f
375375has been finished. These are standard packager scripts as they can be used in any `package.json`.
376376
377377Warning : The use cases for them are very rare and specific and you should investigate first,
378- if your use case can be covered with webpack plugins first. They should never access files
378+ if your use case can be covered with webpack plugins first. They should never access files
379379outside of their current working directory which is the compiled function folder, if any.
380380A valid use case would be to start anything available as binary from `node_modules`.
381381
0 commit comments