rsnext/examples/middleware-matcher/README.md
JTaylor0196 f7baa56792
update example Deploy button URLs (#48842)
### What?
Updates Deploy button URLs for all listed examples here:
https://github.com/vercel/next.js/tree/canary/examples

### Why?
The Deploy URLs are currently broken and result in a failed clone
attempt on Vercel.

### How?
The URLs have been changed from https://vercel.com/new/git/external?… to
-> https://vercel.com/new/clone?…
(Last updated
[here](8eaabe2fb0)
in 2021)
2023-04-26 13:31:44 -04:00

1.7 KiB
Executable file

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:

  1. Middleware always runs first
  2. Middleware always matches _next routes on server side
  3. matcher must always starts with a '/'

Deploy your own

Deploy the example using Vercel:

Deploy with 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).