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.
Hot reloading doesn't update Chrome sourcemaps
See original GitHub issueWe have not merged hot reloading support yet but I noticed a very unfortunate issue: Chrome doesn’t update sourcemaps.
See how the Hello in browser Sources pane doesn’t change.
Note that if we change Webpack devtool setting from cheap-module-source-map to eval it will update on hot reloads:
It used to be broken too but at some point Chrome fixed it. I remember chatting with @paulirish about it in the past.
However we can’t switch to eval mode because we need the source mapping.
We should reach out to somebody at Chrome and figure out if this is fixable. We can live with the broken behavior for a while but if it’s not possible to fix later, then hot reloading experience would be confusing.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:27 (10 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
The fix for
crbug.com/438251has landed and will be available on tomorrow’s Canary.update chrome Version 66.0.3359.117(64-bit) , the bug has fixed. 🙂