Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
yusmar ad78ad4c36 scroll to home pirms 3 gadiem
api hide feature & add discount label pirms 3 gadiem
components scroll to home pirms 3 gadiem
config ganti repo pirms 3 gadiem
lib ganti repo pirms 3 gadiem
pages hide useless feature pirms 3 gadiem
public hide useless feature pirms 3 gadiem
utils ganti repo pirms 3 gadiem
.gitignore ignore .next & pull pirms 3 gadiem
README.md ganti repo pirms 3 gadiem
ecosystem.config.js ecosystem added pirms 3 gadiem
env-example ready live pirms 3 gadiem
jsconfig.json ganti repo pirms 3 gadiem
next.config.js add to cart product pirms 3 gadiem
package.json config global ulang pirms 3 gadiem
products.js ganti repo pirms 3 gadiem
server.js ecosystem added pirms 3 gadiem
store.js ganti repo pirms 3 gadiem
yarn.lock config global ulang pirms 3 gadiem

README.md

Redux example

This example shows how to integrate Redux in Next.js.

Usually splitting your app state into pages feels natural but sometimes you’ll want to have global state for your app. This is an example on how you can use Redux that also works with Next.js’s universal rendering approach.

In the first example we are going to display a digital clock that updates every second. The first render is happening in the server and then the browser will take over. To illustrate this, the server rendered clock will have a different background color (black) than the client one (grey).

The trick here for supporting universal Redux is to separate the cases for the client and the server. When we are on the server we want to create a new store every time, otherwise different users data will be mixed up. If we are in the client we want to use always the same store. That’s what we accomplish on store.js.

All components have access to the Redux store using useSelector, useDispatch or connect from react-redux.

On the server side every request initializes a new store, because otherwise different user data can be mixed up. On the client side the same store is used, even between page changes.

Deploy your own

Deploy the example using Vercel:

Deploy with Vercel

How to use

Execute create-next-app with npm or Yarn to bootstrap the example:

npx create-next-app --example with-redux with-redux-app
# or
yarn create next-app --example with-redux with-redux-app

Deploy it to the cloud with Vercel (Documentation).