3e7f836c28
* Simplified format function in with-redux (#6518) * Update README.md (#6749) - fix runtime configuration example to use `customKey` - standardize warning callouts to use a block quote and bold "**Warning:**" text. Previously there were different ways a warning was mentioned on the docs page: - A warning emoji. The warning emoji didn't render in the actual site. <img width="770" alt="Screen Shot 2019-03-21 at 9 22 21 AM" src="https://user-images.githubusercontent.com/1103708/54759302-c655f380-4bbb-11e9-9116-b0fdc2467bc3.png"> - Italicized "Warning" text. Imo, does not stand out on the page. <img width="663" alt="Screen Shot 2019-03-21 at 9 24 43 AM" src="https://user-images.githubusercontent.com/1103708/54759376-f604fb80-4bbb-11e9-85c6-6589b7738dee.png"> * Adde example on how to rendering muiltiple items carousel on server-side with nextjs |
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| pages | ||
| package.json | ||
| README.md | ||
| store.js | ||
Redux example
How to use
Using create-next-app
Execute create-next-app with Yarn or npx 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
Download manually
Download the example:
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-redux
cd with-redux
Install it and run:
npm install
npm run dev
# or
yarn
yarn dev
Deploy it to the cloud with now (download)
now
The idea behind the 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 Redux Provider is implemented in pages/_app.js. Since the MyApp component is wrapped in withReduxStore the redux store will be automatically initialized and provided to MyApp, which in turn passes it off to react-redux's Provider component.
All pages have access to the redux store using 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.
The example under components/counter.js, shows a simple incremental counter implementing a common Redux pattern of mapping state to props. Again, the first render is happening in the server and instead of starting the count at 0, it will dispatch an action in redux that starts the count at 1. This continues to highlight how each navigation triggers a server render first and then a client render when switching pages on the client side
For simplicity and readability, Reducers, Actions, and Store creators are all in the same file: store.js