Error with generated lambda handler about aws-lambda-typescript

[ammulder]

Seems like it is solved by adding libraryTarget: "commonjs2" in the Webpack config in gulp-webpack-typescript-pipeline:

    output: {
      path: path.join(options.outputDir),
      libraryTarget: "commonjs2",
      filename: '[name].js'
    },

Is there some way to provide that setting as an override from this module?

[ammulder]

I also tried using "gulp lambda:deploy" to deploy to a new Lambda function, instead of my existing one, and I get the same error:

{
"errorMessage": "Handler 'default' missing on module 'index'"
}

As far as I can tell, when Webpack processes the code, it breaks the "export" statement? It's not clear to me what the actual exports in the processed "index.js" are versus what AWS Lambda is looking for.

Finally, for grins, I started a new project, followed the instructions in the README without editing the index.ts at all, put my account settings and a function name into lambda-config.js, and ran "gulp lambda:deploy". So this seems as vanilla as it gets. I get the same error as above.

It seems like I have Webpack 2.6.1 and uglifyJS 2.8.29. If any other info would be helpful, let me know.

[stevejhiggs]

nice catch! I suspect some internal upgrades have broken the upload process. Give me a sec

[stevejhiggs]

ok, please update to 0.0.11 and this should all be fixed. You dont need to regenerate the function it is enough just to regenerate the package. Thanks again for the help