When working with React and Redux and Redux Sagas, I wish I could more easily figure out causal chains for what happens. When I previously did work as a game programmer, for most things (except, say, debugging why things rendered a certain way), you could just go to where the thing happened, put in a breakpoint, and you'd get a beautiful call stack making it easy to reason about how you got to where you are. In my cu…
Is there a reason why the browser debugger is not useful in your case? (or in any other case?) I found it useful for debugging simple jquery websites but I imagine a dozen things can go wrong between the debugger and webpack/next/react/jsx/redux/hot-reload
I think some sort of higher-level debugger ought to be possible, but don't know what it would look like.