Frank Schmid

@RishitKedia I will have a look at that with a local test project later. The `undefined` error is most likely a small confifuration issue with the JSON and the file...

I'm testing right now locally. As soon as I succeed setting up a working configuration I'll write it here so that anyone can test if it really works in a...

Hi there. I got a setup working. In general, I think this is the right way to go, but it may need some additional tweaks and/or small changes (e.g. add...

@azurelogic While implementing and testing my PR I found a few things that might be improved. One of them is e.g. that the plugin introduces aws-sdk as dependency (which is...

I did not use the file-loader at all. Only the things I mentioned in the description. So the the json is just a plain require - nothing else. **Remove the...

This is the complete webpack config I used for testing: ``` const path = require('path'); const slsw = require('serverless-webpack'); const nodeExternals = require('webpack-node-externals'); module.exports = { entry: slsw.lib.entries, target: 'node',...

Ok. That means for some reason your `process.env._HANDLER` is not set. But that should be "only" another configuration issue in one of the files. Can you check that the order...

... and yes. Feel free to create a feature request that demands the optional use of yarn instead of npm for the packaging.

That's strange. The `_HANDLER` environment variable is not set by the secrets plugin, nor is it set by the webpack plugin. It is just evaluated in the client (but that...

I googled a bit and found out that this variable is set online only (in the AWS lambda environment). So I assume that serverless-secrets does not really work with serverless-offline...