57dcc9d329
This command changed in pnpm [6.32.13](https://github.com/pnpm/pnpm/releases/tag/v6.32.13) and [7.1.1](https://github.com/pnpm/pnpm/releases/tag/v7.1.1) so lets update it since its been a few weeks and we can expect pnpm users to update more regularly than npm users. - Fixes https://github.com/vercel/next.js/pull/37240 - Fixes https://github.com/vercel/next.js/pull/37045 - Fixes https://github.com/vercel/next.js/pull/37032 - Fixes https://github.com/vercel/next.js/pull/36602 - Fixes https://github.com/vercel/next.js/pull/36496
1.8 KiB
1.8 KiB
Example app implementing progressive server-side render
Sometimes you want to not server render some parts of your application.
For example:
- Third party components without server render capabilities
- Components that depend on
window
or other browser only APIs - Content isn't important enough for the user (eg. below the fold content)
To handle these cases, you can conditionally render your component using the useEffect
hook.
This example features:
- A custom hook called
useMounted
, implementing this behavior - An app with a component that must only be rendered in the client
- A loading component that will be displayed before rendering the client-only component
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 progressive-render progressive-render-app
# or
yarn create next-app --example progressive-render progressive-render-app
# or
pnpm create next-app --example progressive-render progressive-render-app
Deploy it to the cloud with Vercel (Documentation).