routing-middleware

You can intercept requests before cache by configuring a root middleware.ts or proxy.ts file, which applies platform-level routing logic to inspect and modify requests globally across frameworks. It supports rewrites, redirects, and personalization.

Yes, routing middleware supports Edge, Node.js, and Bun runtimes. You must ensure correct runtime selection and careful matcher configuration to guarantee safe and predictable request handling across your chosen environment.

The middleware.ts and proxy.ts files serve as root configuration points for platform-level request interception. The Skill provides migration guidance between these files specifically for Next.js 16 to maintain predictable routing logic.

You configure rewrites and redirects at the platform level by defining routing logic within a root middleware.ts or proxy.ts file. This allows you to apply global routing decisions across frameworks before requests hit the cache.

You should avoid platform-level routing middleware without understanding correct file placement, runtime selection, and careful matcher configuration, as improper setup can lead to unpredictable request handling and bypassed cache layers.