66597be8a7
### Reason for making this change https://yarnpkg.com/getting-started/qa#:~:text=yarn%2Finstall%2Dstate.,your%20workspaces%20all%20over%20again. In the official documentation of `yarn`, it is stated that `.yarn/install-state.gz` is an optimization file that developer shouldn't ever have to commit. However, currently, when running `create-next-app`, `.yarn/install-state.gz` is being commited. ### Remaining work I apologize for only modifying one template initially to initiate the discussion first. If this change is agreed upon, it should be synchronized with other `.gitignore` templates. Would it be possible to follow a similar approach as in https://github.com/vercel/next.js/pull/47241? I would appreciate any assistance in syncing this change. |
||
|---|---|---|
| .. | ||
| components | ||
| pages | ||
| .gitignore | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
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.
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 dynamic-routing dynamic-routing-app
yarn create next-app --example dynamic-routing dynamic-routing-app
pnpm create next-app --example dynamic-routing dynamic-routing-app
Deploy it to the cloud with Vercel (Documentation).