Middleware

Put request middleware in middleware.ts at the project root. Scope it with a config.matcher export and it runs on the Edge runtime.

officialNext.js docs (Pages Router and v13 to v14 era)confidence 55%current as of Jun 2024

The established pattern is a middleware.ts file at the project or src root that exports a middleware function. You limit which paths it runs on with an exported config.matcher. It runs on the Edge runtime by default. Next.js 16 deprecated this in favor of proxy.ts on the Node.js runtime.

Related claims

is superseded by

On Next.js 16 request interception moves to proxy.ts which runs on the Node.js runtime. Rename middleware.ts to proxy.ts and export a proxy function.

Next.js 16 replaced middleware.ts with proxy.ts on the Node.js runtime. The middleware.ts filename is deprecated though it still runs for Edge cases.