You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
jefry 10809e0251 ecosystem added 3 years ago
.next ecosystem added 3 years ago
api diminta buat deploy 3 years ago
components diminta buat deploy 3 years ago
config ganti repo 3 years ago
lib ganti repo 3 years ago
pages diminta buat deploy 3 years ago
public fix otr price 3 years ago
utils ganti repo 3 years ago
.env ecosystem added 3 years ago
.gitignore deploy 3 years ago
README.md ganti repo 3 years ago
ecosystem.config.js ecosystem added 3 years ago
env-example ganti repo 3 years ago
jsconfig.json ganti repo 3 years ago
next.config.js add to cart product 3 years ago
package.json ecosystem added 3 years ago
products.js ganti repo 3 years ago
server.js ecosystem added 3 years ago
store.js ganti repo 3 years ago
yarn.lock ecosystem added 3 years ago

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