Breakpoints not getting hit on initial page load in Chrome Dev Tools about react-slingshot HOT 9 CLOSED

I just came across this because I was having the same issue. This setting worked fixed the issue:

devtool: '#inline-source-map'

from react-slingshot.

I just confirmed the production build honors breakpoints just fine, so this is indeed related to the webpack devtool setting. The prod build uses source-map which works fine. The issue is: eval-source-map doesn't hit breakpoints on load. I've confirmed switching the devtool setting to eval for dev work fixes this bug. Per the docs, eval also runs faster: https://webpack.github.io/docs/configuration.html#devtool

I'll consider switching this setting tomorrow.

from react-slingshot.

As you can see, it works for me. Can you try setting a breakpoint on this same spot I'm hitting in my screenshot and see if it sticks? Be sure to note that I'm setting a breakpoint on the file under webpack://

from react-slingshot.

Thank you so much for the help. It must be something on my end. Here I try to break on that same line, with no luck.

from react-slingshot.

@nhalloran it works for me too. Sometimes a hard reload in Chrome does the trick. Also ensure that caching is disabled when Chrome dev tools are open.

from react-slingshot.

Oh!!
I should also say that I am looking to break during the initial load. I do get a break on that line when I edit the form, triggering the action. I do not get a break on lines of code that run during the init, for example:

from react-slingshot.

Yes, I can confirm that break points aren't getting hit on initial page load. Perhaps a different source-map setting in Webpack will resolve that. Another simple approach: Just type debugger and it'll hit that breakpoint on load just fine.

from react-slingshot.

Good to know. The debugger command is a great workaround. Thanks!

Also note that I tested it with the official redux examples, i.e.
https://github.com/rackt/redux/tree/master/examples/counter
...and the behavior is the same, so it's clearly a pretty general "issue" - perhaps not necessary to track here.

Thanks again - building my app on this!

from react-slingshot.

Given your comment, I'm going to leave the debugger setting as is for now and close this issue. The eval devtool supports breakpoints on load, but provides a less useful debugging experience otherwise. So I don't see any good changes to make. Thankfully, debugger effectively works around the admitted quirk. Thanks!

from react-slingshot.