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 |
Catch All Routes Example
This example shows how to use Catch all routes in Next.js, which allows a dynamic route to catch all paths.
The catch all page is in pages/post/[...slug]
, it matches any path after /post
, like the following:
/post/first-post
,/post/2020/first-post
/post/2020/first-post/with/catch/all/routes
- Anything that matches the glob
/post/**
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 catch-all-routes catch-all-routes-app
yarn create next-app --example catch-all-routes catch-all-routes-app
pnpm create next-app --example catch-all-routes catch-all-routes-app
Deploy it to the cloud with Vercel (Documentation).