mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00

History

James Hegedus b1d8b839dd Examples: use npx and yarn create to run create-next-app on examples (#4002 ) * remove global npm install of create-next-app * add npx to create-next-app command in examples * add bash to shell snippets * add yarn create to next-app command in examples * fix READMEs named with lowercase * change READMEs to use UPPERCASE		2018-03-14 09:09:46 +01: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	Upgrade React for all examples (#3113 )	2017-10-17 08:11:46 +02:00
README.md	Examples: use npx and yarn create to run create-next-app on examples (#4002 )	2018-03-14 09:09:46 +01:00

README.md

Example app with page loading indicator

How to use

Using `create-next-app`

Download create-next-app to bootstrap the example:

npx create-next-app --example with-loading with-loading-app
# or
yarn create next-app --example with-loading with-loading-app

Download manually

Download the example or clone the repo:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/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.