8d45aa9bfb
### What? When I ran `npx create-next-app --example with-turbopack` and installed dependencies using `yarn`, I found an typescript error(`'SomeComponent' cannot be used as a JSX component.`). <img src="https://github.com/vercel/next.js/assets/51700274/f6c7e478-c0b1-4ea2-996f-4c0c78e3bb4b" width=400 /> and I realized that the bug is due to the version of @types/react(18.0.x). you can check this issue on [here](https://github.com/vercel/next.js/issues/42292#issuecomment-1594351684) too. ### Why? It seems that there is an error occurring in the @types/react version 18.0.x. ### How? It would be good to change the @types/react version to 18.2.8 in the next.js examples. I think this change will resolve [this issue](https://github.com/vercel/next.js/issues/55080#issue-1884846177) [NestJS documentation](https://nextjs.org/docs/app/building-your-application/configuring/typescript#async-server-component-typescript-error) also states to upgrade the version. Co-authored-by: Lee Robinson <me@leerob.io> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .gitignore | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Zustand example
This example shows how to integrate Zustand 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 Zustand 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).
To illustrate SSG, go to /ssg and to illustrate SSR go to /, those pages are using Next.js data fetching methods to get the date in the server and return it as props to the page, and then the browser will hydrate the store and continue updating the date.
The trick here for supporting universal Zustand 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 with the initialZustandState returned from the get*Props methods.
All components have access to the Zustand store using useStore() returned store.ts file.
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-zustand with-zustand-app
yarn create next-app --example with-zustand with-zustand-app
pnpm create next-app --example with-zustand with-zustand-app
Deploy it to the cloud with Vercel (Documentation).