is using redux with next.js based app is considered anti-pattern or we are supposed to use redux even with next.js application like all other react applications.
We're a place where coders share, stay up-to-date and grow their careers.
is using redux with next.js based app is considered anti-pattern or we are supposed to use redux even with next.js application like all other react applications.
Adam Coster -
Marko Denic -
Manuel Vila -
Bello -
Discussion
I use easy-peasy.now.sh/ with my next.js project. I would recommened redux but use a library like this to reduce the boilerplate. One thing thats nice about using Redux is you can take advantage of Redux dev tools which can be very useful.
There's an official example with redux in the nextjs repo: github.com/vercel/next.js/tree/can...
So I'd say, not an anti pattern.
This question could be rephrased as: "Is it Necessary to use Redux with a React.js application" :)
Next.js is just a framework on top of React which simplifies Server Side Rendering setup, but it is still React. And React/Redux combo is very popular and still often used, also by me, so the answer is - it is not necessary, but totally possible! The bigger the app and the more you like functional programming, the better chance Redux will be a good option!
Not an anti pattern, you can use it if you want but it’s not necessary, personally I would recommend zustand github.com/pmndrs/zustand
It depends on types of app you build. Do you need global state ? If yes, then Redux is useful, else Redux is unnessessary.
there is no need for it. You can use the context api instead.