reselect VS redux-toolkit

- Throws better errors in an RSC environment

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

## Reselect 5.0:

- Switches to a new `weakMapMemoize` memoizer as default

- Renames `defaultMemoize` to `lruMemoize`

- Allows passing memoizer options direct to `createSelector`

- Many TS improvements

- https://github.com/reduxjs/reselect/releases/tag/v5.0.1

## Redux Thunk 3.0:

- Drops the default export and switches to named exports ( `{thunk, withExtraArgument}` )

- https://github.com/reduxjs/redux-thunk/releases/tag/v3.1.0

This has been a _huge_ year-long development effort!

We're thrilled to get these improvements out. The tooling and bundle improvements will help all users, and we think the features and TS changes will improve the Redux dev experience significantly.

Thank you SO MUCH to everyone who has contributed or helped test out the work!

Please file bug reports for the inevitable issues that pop up post-release!

but now I'm going off on a conf trip and going to take a very well-earned break from Redux work for December :)

reselect -> For making faster queries to store.

Reselect solves this problem by memorizing the values and only passing what’s necessary.

In addition, diagnosing bugs in how data flowed through the application (where data originated from, how it was changed, etc.) was always super painful because I had to backtrack through selectors referencing selectors referencing selectors. And updating high-level selectors risked breaking something else down the line (even with 100% business logic coverage this was a problem). (This may be chalked up to improper usage of reselect, but I'm curious to hear your thoughts. Is this a common problem?)

reselect : Selector library to optimize your store access

Reselect documentation:

Applying memoization to TypeScript and ReactJS is relatively straightforward. There are several libraries available that provide memoization functionality, such as memoize function from Lodash, reselect or hooks from ReactJS. These libraries can be installed using NPM or Yarn and used in your TypeScript and ReactJS projects.

Generally, all you would need is to have your redux store provider at the very top level of your application (You could also only wrap the components that you want to have this data available to). Then, any component rendered inside that provider can get access to the redux store. The suggested approach ever since hooks were released is to use `useSelector` and `useDispatch` within your component to get the state data that you need. Using a selector library like Reselect is prevalent and keeps your data selection tidy & handles memoization for you.

Reselect is a library for creating memoized “selector” functions. Commonly used with Redux, to slice state and provide just the necessary subtree to a React component.

In my example I am using Redux Toolkit and I got a prompt for actions to login and logout the user. If I need more functions, I can simply start typing the name, and Copilot provides the completion. For instance, in the example, I'm adding a function to update the user. And of course at the end of the file it suggests the exports.

Check out the official documentation.

Redux Toolkit 2.0

Redux Toolkit 2.0 is almost here! Hopefully shipping by this weekend :) Migration page

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*

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

However, Redux, or pure Redux to be specific, can be quite verbose and boilerplate-heavy. It requires a significantly lengthy setup, which is where Redux Toolkit comes in handy, offering a simplified and more efficient way to set up and manage state in your React applications.

State manager is a tool or library that helps manage the state of an application. It provides a centralized store or container for storing and managing data that can be accessed and updated by different components in the application. A state manager solves several problems. Firstly, it is a good practice to separate data and the logic related to it from components. Secondly, when using local state and passing it between components, the code can become convoluted due to the potential for deep nesting of components. By having a global store, we can access and modify data from any component. Alongside React Context, Redux or MobX are commonly used as state management libraries. Learn more Learn more