1b67dc163d
`as` prop is no longer required on `next/link` components for dynamic routes |
||
---|---|---|
.. | ||
components | ||
pages | ||
.gitignore | ||
package.json | ||
README.md |
Dynamic Routing example
This example shows how to do dynamic routing in Next.js. It contains two dynamic routes:
pages/post/[id]/index.js
- e.g. matches
/post/my-example
(/post/:id
)
- e.g. matches
pages/post/[id]/[comment].js
- e.g. matches
/post/my-example/a-comment
(/post/:id/:comment
)
- e.g. matches
These routes are automatically matched by the server.
You can use next/link
as displayed in this example to route to these pages client side.
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 dynamic-routing dynamic-routing-app
# or
yarn create next-app --example dynamic-routing dynamic-routing-app
Deploy it to the cloud with Vercel (Documentation).