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 | ||
public | ||
.eslintrc.json | ||
.gitignore | ||
middleware.ts | ||
next-env.d.ts | ||
next.config.js | ||
package.json | ||
README.md | ||
tsconfig.json |
Middleware
This example shows how to use Middleware in Next.js to run code before a request is completed.
The index page (pages/index.tsx
) has a list of links to pages with redirect
, rewrite
, or normal behavior.
On the Middleware file (middleware.ts
) the routes are already being filtered by defining a matcher
on the exported config. If you want the Middleware to run for every request, you can remove the matcher
.
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 middleware-app
yarn create next-app --example middleware middleware-app
pnpm create next-app --example middleware middleware-app
Deploy it to the cloud with Vercel (Documentation).