f3ef4e99b0
We want to make sure that our examples are not breaking. We don't want to be slowed down by broken 3rd party packages, but we need to ensure that examples covering next.js features are always green. Added as a standalone workflow that doesn't parallelize. It will just run on a cron schedule, so we can check for current status. We can add Slack ping later if we need to. The workflow tests just that our examples can build, so mostly TS issues. We could definitely follow up with actual tests, but that is not as low-hanging. --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by: Tim Neutkens <tim@timneutkens.nl> |
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Example app utilizing next/router for routing
This example features:
- An app linking pages using
next/routerinstead of<Link>component. - Access the pathname using
next/routerand render it in a component
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example using-router using-router-app
yarn create next-app --example using-router using-router-app
pnpm create next-app --example using-router using-router-app
Deploy it to the cloud with Vercel (Documentation).