Bug: Source maps don't work with hot reload
See original GitHub issueIn the console I get an output like index.jsx:6 "test1"
and that’s okay.
But when I save the file, it turns like VM335:18 "test2"
.
I have to refresh the page to see this one index.jsx:6 "test2"
.
So source maps don’t work unless I refresh the page.
Software | Version(s) |
---|---|
Parcel | 1.5.0 |
Node | 9.2.0 |
npm/Yarn | 5.6.0/1.3.2 |
Operating System | MacOS 10.13.2 |
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Webpack dev server, Hot reload and source maps - Medium
Throughout this article we will cover the following subjects 1- Setting up Webpack dev server 2- Hot reloading 3- Source maps.
Read more >Issue 438251: DevTools: Source maps and ... - Monorail
Issue 438251 : DevTools: Source maps and referenced source do not seem to reload on dynamically re-loading javascript. Reported by schedule bhau.
Read more >Source Maps not working with Webpack - Stack Overflow
I'm pretty new to webpack and having some trouble configuring it to produce the necessary source maps. In the devtools it says.
Read more >4 Reasons Why Your Source Maps are Broken - Sentry Blog
This likely means that your source map doesn't contain or link to your original source files. Without your original source files, you're still ......
Read more >Pressing Reload in a webpack + hot reloader + React ...
We used to have a bug where the new debugger didn't forcefully turn off sourcemaps on the server (bug 1303177). What this means...
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
A workaround for the browser bugs would be somehow evaluating the new code via a
<script>
tag.Thanks for looking at this, let me know if you’d like me to lend a hand with anything 🙂