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/with-loading
History
Arunoda Susiripala 399e510389 Make sure lastAppProps always have some value. (#829) 
* Make sure lastAppProps always have some value.

* Revert "Make sure lastAppProps always have some value."

This reverts commit b4ae722d9c1a4460e17dbdc041b111cbd492b2aa.

* Throw an error, if we found an empty object from getInitialProps.

* Add proper tests for getInitialProps empty check.
2017-01-20 11:33:46 -08:00
..
components Implement Router Events (#511) 2016-12-30 17:15:22 -08:00
pages Make sure lastAppProps always have some value. (#829) 2017-01-20 11:33:46 -08:00
static Implement Router Events (#511) 2016-12-30 17:15:22 -08:00
package.json Implement Router Events (#511) 2016-12-30 17:15:22 -08:00
README.md Fix link (#789) 2017-01-16 18:23:24 -03:00

README.md

Example app with page loading indicator

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/with-loading
cd with-loading

Install it and run:

npm install
npm run dev

Deploy it to the cloud with now (download)

now

The idea behind the example

Sometimes when switching between pages, Next.js needs to download pages(chunks) from the server before rendering the page. And it may also need to wait for the data. So while doing these tasks, browser might be non responsive.

We can simply fix this issue by showing a loading indicator. That's what this examples shows.

It features:

  • An app with two pages which uses a common Header component for navigation links.
  • Using next/router to identify different router events
  • Uses nprogress as the loading indicator.