Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong stack trace with webpack

See original GitHub issue

I’m getting this:

TypeError: Cannot read property 'length' of undefined
    at t.handler (/var/task/webpack:/src/main.ts:16:38)
    at invoke (/var/runtime/node_modules/awslambda/index.js:285:5)
    at InvokeManager.start (/var/runtime/node_modules/awslambda/index.js:151:9)

I think the webpack: part should not be there.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:8

Top GitHub Comments

6reactions

tonyfromundefinedcommented, Nov 21, 2019

https://webpack.js.org/configuration/output/#outputdevtoolmodulefilenametemplate

here is the solution

module.exports = {
  output: {
    path: path.resolve(__dirname, './dist'),
    devtoolModuleFilenameTemplate: '../[resource-path]',
  },
}

1reaction

tonyfromundefinedcommented, Nov 28, 2019

If your webpack build environment is the same as your Node.js running environment (usually at development time), you can provide [absolute-resource-path] with the devtoolModuleFilenameTemplate option.

If it is different (using CI/CD), it is better to use relative paths. (ex: ../[resource-path])

And I decided to use Sentry’s Release feature. (upload webpack bundle and sourcemap file in Sentry in release time (in the CircleCI), Sentry merge them and show proper stack trace)

https://docs.sentry.io/workflow/releases