f52955ec94
Clean up package.json files in the `examples` directory: - Add `private: true` - Remove `version` (because they are irrelevant for packages that are not meant to be published) - Remove `name` (because they are optional for packages that are not meant to be published, and when someone clones an example, they often rename it and the property becomes stale) - Remove `author` - Remove `description` - Remove `license` Also remove `with-dynamic-app-layout` example completely, since it does the same as `layout-component` (https://github.com/vercel/next.js/pull/27121#discussion_r668178408). ## Documentation / Examples - [x] Make sure the linting passes |
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
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
windowor 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
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 progressive-render progressive-render-app
# or
yarn create next-app --example progressive-render progressive-render-app
Deploy it to the cloud with Vercel (Documentation).