-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breakpoints not hitting in Chrome #103
Comments
Chrome was just having a hissy fit it seems :) |
This issue appears to be present in latest release - I can set breakpoints but they are never hit. I'm using the example here https://github.com/milankinen/livereactload/tree/master/examples/03-build-systems UPDATE: Breakpoints are hit in Firefox |
Hi @kyle-ssg & @itsravenous! Have you noticed that LiveReactload suffixes reloaded script files with If anyone knows solutions to this issue, all help is welcome! |
@milankinen thanks for the swift response! I saw the rev= issue initially, but it goes away after first refresh (yep, super weird I know) and Chrome shows my breakpoints persisting on reload; they just aren't getting hit! |
Wait, I lied :D Yes, when I make an edit to a component, a |
If I add a |
OK, so breakpoints that should be hit when the page is [re]loaded aren't hit, but if I place a breakpoint in the |
Can you try again with 3.3.0 please? |
Thanks for making this, it's going to make life so much easier once it's all setup!
Having integrated this into my gulp process I'm finding that none of my breakpoints hit in chrome (prior to any patching). Weirdly enough this all seems fine in Firefox.
Any guidance would be greatly appreciated.
The text was updated successfully, but these errors were encountered: