Middleware

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.

officialNext.js 16 release announcementconfidence 90%current as of Aug 2026

Next.js 16 renamed the middleware entry point to proxy.ts to make the network boundary explicit. proxy.ts runs on the Node.js runtime. You rename middleware.ts to proxy.ts then rename the exported function to proxy while the logic stays the same. The middleware.ts filename still works for Edge cases but is deprecated.

Related claims

supersedes

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

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.