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.
Find a way to preserve line numbers in error messages / stack traces
See original GitHub issueSeeing incorrect line numbers in stack traces breaks workflow too much.
We could try to either use line preserving code transformations (does Babel support that?) or enable more advanced Webpack’s devtool (cheap-module-eval-source-map).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:12 (7 by maintainers)
Top Results From Across the Web
How to keep original line numbers in stack traces with R8?
If it is possible to get the original stacktrace from the user in the Google Play Console, then it is possible to run...
Read more >Unable to get line numbers in error report stack traces
NET WPF project. I am testing error reporting feature and no matter what I do I can't get any line numbers in stack...
Read more >Line numbers in stack trace - Microsoft Q&A
The line numbers are in the pdb file. This file is used by the debugger and the debug build to sync to the...
Read more >How to get Java source in applet stack trace to debug Java ...
I unzipped src.zip in my JDK directory and set the debug flag for my Ant <javac> task as well as set debuglevel to...
Read more >R8 does not obey '-keepattributes LineNumberTable' when ...
All the information is there for stack traces if you keep the line number table with keepattributes. We remap the line numbers to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I strongly believe that source maps is better than no source maps even in the current state. We should definitely file issues with upstream projects, but in the short term I’m not aware of any development teams that intentionally disable source maps in development.
@gaearon I don’t understand. In my installation (“react-scripts”: “0.6.1”), everything is just one big bundle.js.