7e2d476e44
* Remove micro example * Remove page that uses getInitialProps * Update with-docker example * Update dynamic import example * Update Fela example * Update Flow example * Update framer motion example * Remove freactal example * Remove with-higher-order-component * Remove with-immutable-redux-wrapper as it shows avenues to performance issues * Remove example that doesn't have usage * Update with-kea * Remove example that is not used * Update next-page-transitions example * Remove next-routes example as dynamic routes are supported by default * Add link to documentation * Update Overmind example * Update pretty-url-routing example * Remove update with low usage * Update with-react-ga example * Update React Helmet example * Remove mobile-detect from carousel example * Remove react-useragent as it shows a bad practice * Remove react-uwp example as it has low usage * Remove recompose example as it shows outdated practices * Remove refnux example as it has low usage * Remove example that can be created using api routes * Update with-segment-analytics * Update socket.io example * Remove socket.io example as it's shows bad practices * Update static export example * Update universal configuration example |
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| 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.
Deploy your own
Deploy the example using ZEIT Now:
How to use
Using create-next-app
Execute create-next-app with npm or Yarn to bootstrap the example:
npm init next-app --example with-next-page-transitions with-next-page-transitions
# or
yarn create next-app --example with-next-page-transitions with-next-page-transitions
Download manually
Download the example:
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-next-page-transitions
cd with-next-page-transitions
Install it and run:
npm install
npm run build
npm start
Deploy it to the cloud with ZEIT Now (Documentation).