Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for source mapping #188

Closed
schof opened this issue Aug 9, 2019 · 3 comments
Closed

Support for source mapping #188

schof opened this issue Aug 9, 2019 · 3 comments
Labels

Comments

@schof
Copy link

schof commented Aug 9, 2019

It would be cool if lambda-local supported source mapping so we could make better use of stack traces

@gpotter2
Copy link
Collaborator

Hi,
Thanks for the suggestion. Could you point to a doc / examples of what you mean by that ?
Thanks

@schof
Copy link
Author

schof commented Aug 12, 2019

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.

@gpotter2
Copy link
Collaborator

gpotter2 commented Jan 17, 2020

FTR project has now migrated to TypeScript therefore creating a source map should be easily manageable with tsc --declarationMap..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants