1865a6e3d9
### What? The team working on vercel.com reported that multiple pages were being compiled when opening a single page. Investigated this a bit and found it was caused by the matching logic (that also triggers compiling of matched pages) running before middleware runs. ### How? Removed this matcher logic, as far as I can tell it's not actually being used. Probably a leftover from when we provided `page` as a middleware parameter before we made middleware run in front of all resolving. Fixes NEXT-999 Fixes NEXT-806 <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
7 lines
241 B
TypeScript
7 lines
241 B
TypeScript
import { NextRequest, NextResponse } from 'next/server'
|
|
|
|
export default function middleware(request: NextRequest) {
|
|
if (request.nextUrl.pathname === '/about') {
|
|
return NextResponse.rewrite(new URL('/new-about', request.nextUrl))
|
|
}
|
|
}
|