mirror of
https://github.com/terribleplan/next.js.git
synced 2024-01-19 02:48:18 +00:00
7e12997af6
I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder. |
||
---|---|---|
.. | ||
components | ||
pages | ||
package.json | ||
README.md |
Example app implementing progressive server-side render
How to use
Using create-next-app
Execute create-next-app
with Yarn or npx 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
Download manually
Download the example:
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/progressive-render
cd progressive-render
Install it and run:
npm install
npm run dev
# or
yarn
yarn dev
Deploy it to the cloud with now (download)
now
The idea behind the example
Sometimes you want to not server render some parts of your application. That can be third party components without server render capabilities, components that depends on window
and other browser only APIs or just because that content isn't important enough for the user (eg. below the fold content).
In that case you can wrap the component in react-no-ssr
which will only render the component client-side.
This example features:
- 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