5629223407
[With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples need to be updated, so the following snippet updated all the examples to a compatible react version. ```bash cd examples/ fd -g 'package.json' | xargs sed -r -i 's/"react": ".*"/"react": "^17.0.2"/ fd -g 'package.json' | xargs sed -r -i 's/"react-dom": ".*"/"react-dom": "^17.0.2"/' # exclude experimental react version git checkout with-reason-relay/package.json ``` |
||
|---|---|---|
| .. | ||
| components | ||
| overmind | ||
| pages | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
Overmind example
This example uses overmind.
Preview
Preview the example live on StackBlitz:
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app with npm or Yarn to bootstrap the example:
npx create-next-app --example with-overmind with-overmind-app
# or
yarn create next-app --example with-overmind with-overmind-app
Deploy it to the cloud with Vercel (Documentation).
Notes
Look at the comments for more information on how the application is structured. This is just one of several ways you can manage hydration and rehydration of state. It depends heavily on how you want to manage it, do code sharing between client and server etc. The exampled approach should give you the hooks and flexibility to get you started on your endeavor :-)