3ad55721d1
**Reasons for making this change:**
- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have
a period at the beginning of the filename
Links to documentation supporting these rule changes:
**Changelog with proof here:**
|
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| .gitignore | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
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
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
yarn create next-app --example progressive-render progressive-render-app
pnpm create next-app --example progressive-render progressive-render-app
Deploy it to the cloud with Vercel (Documentation).