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.
pace-src screws up source mapping
See original GitHub issuetried setting my vendor and local source file to use the pace-src and then threw a debugger statement in my code. Chrome can’t map the source and just throws the breakpoint in the app-start.js
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Source maps not working? · Issue #3750 · parcel-bundler/parcel
It seems like switching to Parcel has somehow screwed up an import ? But ALL the stack traces are minified code with no...
Read more >4 Reasons Why Your Source Maps are Broken - Sentry Blog
Here are four reasons why your source maps are broken and tips on how to ... agents to locate and link up all...
Read more >What is wrong with SOURCE MAPS and how not to mess with ...
Thus, one of the main reasons for using DSL is the ability to write simple and concise code that is easy to learn,...
Read more >Improving Development with Source Maps for Debugging
Setting up source maps for webpack is very straightforward. In the module.exports object, we'll add a new configuration option that's built-in ...
Read more >Webpack & TypeScript Setup #6 - Source Maps - YouTube
Webpack & TypeScript Setup #6 - Source Maps. Watch later. Share. Copy link. Info. Shopping. Tap to unmute. If playback doesn't begin shortly ......
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 reverted the ‘pace-src’ script load to standard ‘src’ and my debugging ability returned (that is the source code mapped properly) AND ember-cli-pace is still working. Does this make any sense?
Hey folks. Going to try to look into this and see if I can reproduce and track down why this might be happening.
If someone is able to put up a repo with the minimum test case with steps to reproduce, that would be really helpful.