077097b7f8
* Add licences to all example/package.json that lack them * Revert "Add licences to all example/package.json that lack them" This reverts commit 5d4e25012f7334772b8ef5924bc355277e827cba. * Update check-examples to remove `license` field from examples * Remove `license` from all examples. This was mentioned in vercel/next.js#27121 but it looks like it didn't end up being in the merge? Co-authored-by: JJ Kasper <jj@jjsweb.site> |
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
next-page-transitions example
The next-page-transitions library is a component that sits at the app level and allows you to animate page changes. It works especially nicely with apps with a shared layout element, like a navbar. This component will ensure that only one page is ever mounted at a time, and manages the timing of animations for you. This component works similarly to react-transition-group in that it applies classes to a container around your page; it's up to you to write the CSS transitions or animations to make things pretty!
This example includes two pages with links between them. The "About" page demonstrates how next-page-transitions makes it easy to add a loading state when navigating to a page: it will wait for the page to "load" its content (in this examples, that's simulated with a timeout) and then hide the loading indicator and animate in the page when it's done.
Preview
Preview the example live on StackBlitz:
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app with npm or Yarn to bootstrap the example:
npx create-next-app --example with-next-page-transitions with-next-page-transitions-app
# or
yarn create next-app --example with-next-page-transitions with-next-page-transitions-app
Deploy it to the cloud with Vercel (Documentation).