redux-batch | Enhance your Redux store to support batched actions | State Container library

tailwindcss v3 only supports Postcss8 and only create-react-app v5 supports Postcss8 for now. So you need to upgrade the create-react-app to v5. No need for craco in create-react-app v5 as well

First make sure to checkout to different branch or push your code to github before migrating, just for safety.

1.First run npm uninstall @craco/craco autoprefixer postcss tailwindcss
Delete the craco.config.js file
Delete the tailwind.config.js
Now just follow the offical tailwindcss docs
2. Run npm install -D tailwindcss postcss autoprefixer
3. npx tailwindcss init -p
copy paste the tailwind.config.js file from tailwindcss docs
4. npm install react-scripts@latest
5. Now npm start

Later paste your previous tailwind.config theme in the new tailwind.config.js file.

The order of steps may or may not matter but following this steps worked for me.

I was aware that the "--max-old-space-size=8192" parameter does not pass to build. So I dedided to add ENV in Dockerfile like " ENV NODE_OPTIONS="--max-old-space-size=8192"". Finally my Dockerfile transformed to:

I'm a Redux maintainer and author of Redux Toolkit.

I actually just wrote a blog post entitled A Comparison of Redux Batching Techniques, which covers the various forms of batching available with Redux actions.

As I just commented over in that redux-batch issue:

The unstable_batchedUpdates() usage within React-Redux itself only attempts to minimize the nested re-renders from within a single dispatch. That does not overlap with the goal of this project, which attempts to allow dispatching multiple actions at once while only notifying store subscribers a single time.

Per your original question, I'm not sure that you can use React-Redux's batch() API correctly in sagas, because of the need to yield put(). The batch() API (which is just React's own unstable_batchedUpdates() API, re-exported) relies on tracking any React state updates that are queued during a single event loop tick, and I suspect that use of generators may not work with that. I'd have to see examples in action to be sure.

In any case, per the blog post, there's several options for batching, which work in different ways. It's all a question of what actual use case you're trying to solve.