You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using Typescript which is "compiled" into regular Javascript and then also combined with other libraries and minified using Webpack. The result is a minified file and a much larger source map.The resulting file is a very ugly, difficult to read source file (but nice and light for lambda upload, etc.)
There is a way to show the original line numbers, etc. in any stack traces that are generated but I'm not sure exactly how it's done (just that it can be done.) Javascript tools like Sentry.io allow you to reference a source map so that they can show you the original line numbers, etc. in the stack trace.
It would be cool if lambda-local supported source mapping so we could make better use of stack traces
The text was updated successfully, but these errors were encountered: