History

Hassan El Mghari 33aa51ab26 Change README structure in examples (#35349 ) Changed the README structure in all examples to take out the Stackblitz button and include it as a link instead using a [bash script](https://gist.github.com/Nutlope/a8f3556a5a401e32a8c6278b782ebf8a/revisions). I also added the Vercel deploy button to 15 READMEs that didn't have it.		2022-03-16 21:39:26 +00:00
..
pages	Replace CSS tag with JS import (#28143 )	2021-08-16 03:01:57 +00:00
public	Change to public folder in with-loading example (#9016 )	2019-10-09 17:28:06 -05:00
.gitignore	Added .gitignore to examples that are deployed to vercel (#15127 )	2020-07-16 10:52:23 -04:00
package.json	Remove `licence` from all `example/package.json` that has them (#28007 )	2021-08-14 10:48:39 -05:00
README.md	Change README structure in examples (#35349 )	2022-03-16 21:39:26 +00:00

README.md

Example app with page loading indicator

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, the 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.

Deploy your own

Deploy the example using Vercel or preview live with StackBlitz

How to use

Execute create-next-app with npm or Yarn 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

Deploy it to the cloud with Vercel (Documentation).