routing-middleware

To intercept and rewrite requests at the edge, create a root middleware.ts file and deploy with Vercel to modify web traffic before it hits your application routes. This enables flexible routing and header control across frameworks.

Vercel edge middleware works with Next.js, SvelteKit, Astro, Nuxt, or any framework across Edge, Node.js, and Bun runtimes. It provides a platform-level interception layer to modify or redirect requests consistently.

Scope middleware to specific routes and avoid unnecessary compute by configuring precise matching with config.matcher in your root middleware.ts file. This limits interception to designated paths only.

For Next.js 16, you need to create a proxy.ts file instead of middleware.ts to satisfy runtime configuration and file placement requirements. This handles request interception and migration notes properly.

Edge middleware supports geo-personalization and A/B testing by intercepting requests at the platform level to rewrite or redirect them before they reach your app. This enables dynamic, location-aware routing.