4466ba436b
## Description This PR ensures that the default prettier config is used for examples and templates. This config is compatible with `prettier@3` as well (upgrading prettier is bigger change that can be a future PR). ## Changes - Updated `.prettierrc.json` in root with `"trailingComma": "es5"` (will be needed upgrading to prettier@3) - Added `examples/.prettierrc.json` with default config (this will change every example) - Added `packages/create-next-app/templates/.prettierrc.json` with default config (this will change every template) ## Related - Fixes #54402 - Closes #54409 |
||
|---|---|---|
| .. | ||
| pages | ||
| .gitignore | ||
| middleware.ts | ||
| next-env.d.ts | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
Middleware
This example shows how to configure your Next.js Middleware to only match specific pages.
The index page (pages/index.ts) has a list of links to dynamic pages, which will tell whether they were matched or not.
The Middleware file (middleware.ts) has a special matcher configuration key, allowing you to fine-grained control matched pages.
Please keep in mind that:
- Middleware always runs first
- Middleware always matches
_nextroutes on server side - matcher must always starts with a '/'
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example middleware-matcher middleware-matcher-app
yarn create next-app --example middleware-matcher middleware-matcher-app
pnpm create next-app --example middleware-matcher middleware-matcher-app
Deploy it to the cloud with Vercel (Documentation).