Closed nolde closed 7 years ago
I had fixed this issue in one of my commits, by ignoring the implementation folder structure and updating the handler
configuration for function to reflect that. That structure is pretty meaningless, as browserify packs everything into a single file.
It seems like you have undone that change. Any special reason why? I just ask this because, if I have a simple folder organisation like "functions/functionName/index.js", the plugin fails.
There is any way you could bring that back?
At least in Windows, when using a handler path that is more than one folder deep, the plugin throws an error.