Redux used to be great but if you have tried none of them, I would highly recommend using Redux-Toolkit. The only case where I may want you to stick to redux is when you're using class-based components, where Redux Toolkit does have some boilerplate (like Redux) and you may miss out decent support.
However with functional components, Redux toolkit is like Redux on steroids.
Reason for using Redux toolkit:
A lot lesser boilerplate code is required compared to Redux.
Redux hooks like
useSelectoranduseDispatchmake things so short and easy to use. [This is not specific to Redux toolkit, however, highlighting it here as it is extremely helpful to consume these hooks in functional component and might be helpful for those who are completely new to redux]You don't need to do manual
thunksetup as redux-toolkit comes with out of the boxcreateAsyncThunkwhich enables you to perform async operations in very hassle free way.getStateis also very helpful in obtaining state variables across any of your actions or async operations.Mutability might be considered as advantage or disadvantage, but if you're not too used to writing with spread operators, you might love this feature as well. Do straight assignments and let redux toolkit take care of mutability under the hoods.
currentcan be used to log your state anywhere in case you want to debug and understand where things are going wrong. (Of course, Redux debugger tools are great as well)Prebuilt templates: you might want to use
npx create-react-app my-app --template redux-typescriptor if you're using it with next:yarn create next-app --example with-redux with-redux-app. It gives you a setup readyredux toolkitboiler plate and also contains a boiler plate of most important redux state management applications so that you could refer them to create your own slices very easily.
I have been using a lot of redux and initially it was a bit confusing but once you get a good command over redux toolkit and if you're using a lot of functional components, you probably would never go back to redux again.
Answer from Shivam Sahil on Stack OverflowRedux used to be great but if you have tried none of them, I would highly recommend using Redux-Toolkit. The only case where I may want you to stick to redux is when you're using class-based components, where Redux Toolkit does have some boilerplate (like Redux) and you may miss out decent support.
However with functional components, Redux toolkit is like Redux on steroids.
Reason for using Redux toolkit:
A lot lesser boilerplate code is required compared to Redux.
Redux hooks like
useSelectoranduseDispatchmake things so short and easy to use. [This is not specific to Redux toolkit, however, highlighting it here as it is extremely helpful to consume these hooks in functional component and might be helpful for those who are completely new to redux]You don't need to do manual
thunksetup as redux-toolkit comes with out of the boxcreateAsyncThunkwhich enables you to perform async operations in very hassle free way.getStateis also very helpful in obtaining state variables across any of your actions or async operations.Mutability might be considered as advantage or disadvantage, but if you're not too used to writing with spread operators, you might love this feature as well. Do straight assignments and let redux toolkit take care of mutability under the hoods.
currentcan be used to log your state anywhere in case you want to debug and understand where things are going wrong. (Of course, Redux debugger tools are great as well)Prebuilt templates: you might want to use
npx create-react-app my-app --template redux-typescriptor if you're using it with next:yarn create next-app --example with-redux with-redux-app. It gives you a setup readyredux toolkitboiler plate and also contains a boiler plate of most important redux state management applications so that you could refer them to create your own slices very easily.
I have been using a lot of redux and initially it was a bit confusing but once you get a good command over redux toolkit and if you're using a lot of functional components, you probably would never go back to redux again.
Redux Toolkit is the official recommendation for all Redux code you write since 2019. See the Redux Style guide on this and Why Redux Toolkit is How To Use Redux Today.
I would recommend you start learning Redux by following the official Redux "Essentials" tutorial from the Redux homepage - and that will teach you Redux Toolkit from the beginning.
I am making a project on eCommerce Website using ReactJS and I am confuse that what should I use Redux or Redux Toolkit for state managment.
Redux vs Redux toolkit
What is the difference between React Redux and Redux Toolkit and which one should I learn in 2020?
You use them together.
Per that official tutorial:
-
Redux is the core state management library
-
Redux Toolkit wraps around the Redux core and provides APIs to simplify common Redux use cases
-
React-Redux lets your React components talk to a Redux store, however it was created
So, you'll be creating your store with Redux Toolkit, and passing the store to React-Redux.
Keep reading that official "Redux Essentials" tutorial - it explains how to do all this.
More on reddit.comI don't like redux-toolkit.
zustand vs redux(or redux toolkit) ? which to use for scalable react projects?
Videos
What should i learn redux or redux toolkit?
Thank you :)
Hi, so I was learning Redux from this youtube playlist, which is about a year old. In the aforementioned series, the instructor uses React Redux to create the store and use Redux in a React app.
I was then going through the official tutorial and I found out about Redux Toolkit, which they say is "is our recommended approach for writing Redux logic".
So I am a bit confused now about the difference between them and which library should I use now in 2020.
You use them together.
Per that official tutorial:
-
Redux is the core state management library
-
Redux Toolkit wraps around the Redux core and provides APIs to simplify common Redux use cases
-
React-Redux lets your React components talk to a Redux store, however it was created
So, you'll be creating your store with Redux Toolkit, and passing the store to React-Redux.
Keep reading that official "Redux Essentials" tutorial - it explains how to do all this.
You will use Redux Toolkit to set up your store, slices, and reducers. You will use React-Redux for your useDispatch and useSelector imports.
As a learner, I don't think there is anything wrong with knowing both ways of doing it.
My team has adopted Redux Toolkit across our project and we've found it to be a worthwhile experience.