redux-devtools-extension

If any react noobs are reading this, the best React state management setup for you is Redux+Immer. After some setup, it's easy to use, and the docs are very good and up to date. When I was learning React, I kept putting off Redux because youtube said it was complicated and you didn't need it after useContext. Big mistake. Our app became more complicated because our state management(useState/useContext) was so simple. Switching to Redux dramatically simplified our most complicated components. Also, the Redux dev tools extension is a game changer. It lets you see every state change, in order, with traces and diffs. https://github.com/zalmoxisus/redux-devtools-extension Pros can obviously make up their own mind. I’ve tried Mobx and the tooling just wasn’t there, but I hear their diffing algos are good.

It's worth noting that the Redux DevTools Extension _can_ capture and display a literal stack trace for every dispatched action, if you've enabled that while setting up your store. This allows you to see what part of your app triggered each state update: https://github.com/zalmoxisus/redux-devtools-extension/blob/...

Not general purpose but Redux has forward/reverse time debug tools https://github.com/zalmoxisus/redux-devtools-extension#redux...

FWIW, we recently added a new "action stack trace" feature to the Redux DevTools Extension that helps show exactly where each action was dispatched from [0]. Also, I agree that sagas are not necessary for most apps, and we have some advice in the Redux FAQ on how to choose a side effects handling approach [1]. For most apps, thunks are more than sufficient. [0] https://github.com/zalmoxisus/redux-devtools-extension/blob/... [1] https://redux.js.org/faq/actions#what-async-middleware-shoul...

No, the core Redux store does _not_ store any action history by itself. It's simply: function createStore(reducer) { var state var listeners = [] function getState() { return state } function dispatch(action) { state = reducer(state, action) listeners.forEach(listener => listener()) } } It's the Redux DevTools that do the real work of actually saving an action log, like what was described above. In fact, canceling actions does actually work by re-running the actions in the same sequence, minus the ones that are being skipped, to generate the new state. That logic has been split out into its own package, which you can see in the https://github.com/zalmoxisus/redux-devtools-instrument repo. Very vaguely related side note: earlier this year, I spent

I'm a Redux maintainer. FWIW, I'm always open to suggestions on how we can make using Redux easier and better for everyone (example prior discussion: https://github.com/reactjs/redux/issues/2295 ). We're currently working on a "starter kit" package that's intended to address some of the most common concerns about using Redux, and hope to make it an official Redux-branded package in the near future. I'd appreciate any feedback or ideas you have for improving it: https://github.com/markerikson/redux-starter-kit Also, since you mention stack traces: if anyone out there has a bit of free time on their hands, I'd _love_ to see the Redux DevTools core and extension updated to show a stack trace for where each action was dispatched: https://github.com/zalmoxisus/redux-devtools-extension/issue...

I know the title can sound clickbaity, but I have a personal practical question born from my observations. As an independent developer I a build frontend applications for my clients. I have a set of tools, one of which is [1] Redux DevTools extension for Chrome. Its window is often open while I am working. What I noticed is some major large webapps keep it enabled in production what makes me think they at least use Redux, not necessarily React. I see actions dispatched in the Redux DevTools window while I am performing my tasks in these apps. To name a few - Atlassian apps: Jira and Confluence, and Balsamiq.cloud mocking tool. The other thing I saw is these are large and very slow and seem like devs just applied some common techniques and patterns from Redux world to their large apps without putting much thought into it. So, I wonder (ign