terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity
next.js/examples/progressive-render
History
Lukas Strassel 4a73ccbb00 add react and react dom as peer (#1024) 
- tackles #997
- add ./idea to gitignore for webstorm users
- update all the examples
2017-02-08 10:11:38 +05:30
..
components [example] Progressive rendered application (#998) 2017-02-05 13:43:28 +01:00
pages [example] Progressive rendered application (#998) 2017-02-05 13:43:28 +01:00
package.json add react and react dom as peer (#1024) 2017-02-08 10:11:38 +05:30
README.md [example] Progressive rendered application (#998) 2017-02-05 13:43:28 +01:00

README.md

Example app implementing progressive server-side render

How to use

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/master | tar -xz --strip=2 next.js-master/examples/progressive-render
cd progressive-render

Install it and run:

npm install
npm run 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

Example: https://progressive-render-raceuevkqw.now.sh/