redux-devtools VS redux

Also, you should use redux-devtools extension to get the most out of any react-redux-based project.

Use NgRx's action stream as a logging solution. Dispatch actions instead of logging. You don't have to worry about the state management part or anything either. Add the store-devtools package along with the base store package. It'll let you configure only logging while in development mode and a few other options. Then, install the Redux Devtools extension into your browser. That will give you a view of the dispatched actions and any data you want to pass along with them. It has a filter, so you can tag your actions like you normally would as described in the docs. Like, "[Log Level] [Feature] log message". Then, filter them in the dev tools to see just what you want. You can see a screenshot of it here. You may even like some of its other features and maybe you'll pick up more of the pattern as you see fit.

Redux DevTools is a browser extension that allows developers to inspect and debug Redux stores. This tool helps developers to track state changes, actions, and other data related to the Redux store. You can download it from its official GitHub repository: https://github.com/reduxjs/redux-devtools.

Redux dev tools

You can still keep your custom hooks in separate files, maybe in a folder called state. You could migrate to a state library when things start to seem unmanageable, or when you want one of the many cool features that a state library can offer, like automatically persisting parts of state to your user's storage using middleware (Redux docs, Zustand docs), easily managing API connections and query caching with RTK Query, or having a log of every state change with the ability to revert/go back in time to debug state changes with Redux Devtools (also works with Zustand).

With the redux-devtools-extension, we can now easily see all the actions that have been dispatched, as well as the current state of our store. This extension also allows us to time travel, meaning we can go back and forth through different states to see how our application got to where it is, as shown in the image below.

We need to see your RECEIVE_BENCHES action creator as well as dispatch call to tell you more. You should inspect what is going on in your reducer, either by setting a breakpoint in your editor's debug mode, by using Redux DevTools (https://github.com/reduxjs/redux-devtools), or simply by writing dirty console.log and debugger calls.

When an action is dispatched, all of the reducers will be notified and every single one of them will check if they can handle the action. Not only that, but the Redux dev tools will be a mess trying to see what action was fired when. That’s why we should try to think of actions as events that happened and not what the action is changing. For example, we should rather have an action called userLoggedIn than setUserId.

Redux

redux - Redux is a key tool used in managing state across an application. This can be used with any web technology including React, Vue and Angular docs

Redux is a client-state library.

react-redux: A powerhouse for efficient state management and data flow control. Learn more

Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.

I am _thrilled_ to announce that:

Redux Toolkit 2.0 is LIVE!!!

- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0

This major version has new features, faster perf, smaller bundle size, and removes deprecated options.

It's accompanied by majors for all our Redux family packages

## RTK 2.0:

- a new `combineSlices` method for lazy-loading reducers - Updates to `createSlice` to include a `selectors` field and allow defining thunks inside

- Immer 10 w/ faster updates

- Removal of deprecated options

See the migration guide:

- https://redux.js.org/usage/migrations/migrating-rtk-2

All of the Redux libraries now have modernized packaging with full ESM/CJS compat. They also ship modern JS (no transpiling for IE11), which means smaller bundle sizes.

We've also done byte-shaving work to shrink the bundles (extracting error messages, de-duping imports)

## Redux core 5.0:

- The TS conversion we did in 2019!

- Action types _must_ be strings

- `UnknownAction` as the default action type

- Better preloaded state types

- Internal subscription improvements

- Still marks `createStore` as deprecated!

- https://github.com/reduxjs/redux/releases/tag/v5.0.0

## React-Redux 9.0:

- *Now requires React 18 and RTK 2.0 / Redux 5.0*

DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.

Oh hey, that's my post!

(yes I spend too much time refreshing HN :) )

FWIW I did end up with a packaging combination that seems to work sufficiently. I never did fix the "FalseCJS" issue that `are-the-types-wrong` is detecting. I played with double-emitting TS typedefs, and the `tsup` tool _does_ actually have support for that now (added by Andrew Branch from the TS team). So it might be more feasible now. But ultimately I decided I was tired of messing with packaging setup and that what I've got is good enough. (hopefully)

We're actually about to launch Redux Toolkit 2.0 and Redux 5.0 this week, assuming the last couple pieces come together. Here's the latest RCs - you can see the current `package.json` files in there:

- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0...

- https://github.com/reduxjs/redux/releases/tag/v5.0.0-rc.1