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.
Use source maps
See original GitHub issueHi,
I don’t really understand how this package works so I apologise in advance if this isn’t the right place to make this question.
On my project, the code that reaches the browser is processed by babel. The final code has source maps that google chrome uses to show the original source when I open the dev tools. However the puppeteer coverage information of a file shows the processed source code, not the original. Is there a way to convert the text and ranges fields of the coverage object to the original source and line numbers?
Thank you for your antention
Issue Analytics
- State:
- Created 5 years ago
- Reactions:15
- Comments:20 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@stevenvachon the newest version of
v8-to-istanbulwhich is the library that remaps coverage fromV8format to Istanbul format now supportssource-maps, perhaps try experimenting with this?Without this, the tool is not really useable unfortunately if you’re using any bundler like webpack 😕