Não pode escolher mais do que 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
 
 
Jennyver Seztiani Luxman c5cf1c0fbe make a new Hino web há 2 anos
api make a new Hino web há 2 anos
components make a new Hino web há 2 anos
config make a new Hino web há 2 anos
lib make a new Hino web há 2 anos
pages make a new Hino web há 2 anos
public make a new Hino web há 2 anos
tmp make a new Hino web há 2 anos
utils make a new Hino web há 2 anos
.gitignore make a new Hino web há 2 anos
README.md make a new Hino web há 2 anos
ecosystem.config.js make a new Hino web há 2 anos
env-example make a new Hino web há 2 anos
index.js make a new Hino web há 2 anos
jsconfig.json make a new Hino web há 2 anos
next.config.js make a new Hino web há 2 anos
package.json make a new Hino web há 2 anos
products.js make a new Hino web há 2 anos
sample.env.local make a new Hino web há 2 anos
server.js make a new Hino web há 2 anos
store.js make a new Hino web há 2 anos
yarn.lock make a new Hino web há 2 anos

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