ducks-modular-redux VS redux-thunk

And here's an interesting proposal for organizing data store/reducer logic: https://github.com/erikras/ducks-modular-redux

Yeah, the "ducks" file structure has been around as an idea since 2015, but most Redux apps (and our older docs) used a "folder-by-type" pattern (/reducers/todos.js, /actions/todos.js, etc).

The official Redux Style Guide suggests using the (very modular) Ducks structure. Essentially, this structure follows the design pattern of "New Feature? New folder." I am not 100% sure, but this seems to be a newer development in Redux best practices. For example, favesound-redux splits files into "type" folders.

That's an idea that has been around for awhile and was popularized by the Duck pattern for Redux.

The original Redux docs examples did show a "file-by-type" folder structure (ie, /actions/todos.js, /reducers/todos.js, etc), but you've always been able to structure your code however you want to. The "ducks" pattern was invented right after Redux came out, and has always been a valid approach.

- 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 :)

redux-thunk : For asynchronous operations

Use async logic with Redux "thunk" middleware for handling things like login, data fetching, and handling loading state.

Since it was a relatively low level tool, just like React, that gave a lot of freedom to the user to find different ways to make it work for them. In particular when it came to async operations Redux itself gave no official solution. The most popular options are redux-thunk, redux-observable, and redux-saga. There were probably a dozen more options out there.

Redux Thunk

I recommend https://github.com/reduxjs/redux-thunk if you use Redux with any async data.

As you might have heard, redux-thunk is a very small package. You can see the entirety of the behavior in the following code (reproduced here from the redux-thunk github repo):