Frank Schmid

@ceilfors Cool stuff. Maybe the conditional plugin can be integrated into the sls-webpack project, so that you do not need to install it but just use `slsw.plugins.ConditionalPlugin` in the webpack...

Hi @mcongy , did you try ``` custom: webpack: packagerOptions: scripts: - yarn autoclean --force ``` The scripts option is made especially to execute vustom scripts after installation of the...

You should use `after:webpack:package:packExternalModules`. packageExternal modules executes a npm install, so before would be too early. However, I'm planning to add some kind of exclude pattern (there is already some...

Hi @Vadorequest, thanks for the report 👍 It seems, that you need a missing babel transform in your babel.rc to get rid of `"SyntaxError: Unexpected token import"` Additionally, `@babel/runtime` might...

Hi @austin43 , thanks for the feature request. Integrating `pnpm` needs some analysis before it can be integrated. I checked the docs and saw that it mainly uses hard/soft links...

@austin43 Thanks for the integration experiment. Overall, the integration looks ok (it is quite similar to the npm one - what's expected). The most important thing is, the `static getProdDependencies`...

@austin43 Sounds good. If the tree is the same, it should work without having a special handling.

@hassankhan @deftomat Yes, that's right. The plugin checks the global package setting and either packages all functions separately or as one service zip. In general, there should not be any...

Hi @daniel-cottone , thanks for reporting. This can be something with your configuration. SLS-webpack since 3.0.0 requires that you use slsw.lib.entries for your entry definitions and have the function handlers...

The handlers look good. However, version 2.x did not support individual packaging (in fact it only copied the whole artifact per function). So you should, as next step, add node...