nextjs-16-proxy

To migrate from middleware.ts to proxy.ts in Next.js 16, rename the file in your src directory root and adjust the export function name. This Skill provides the exact template for updating your network boundary tasks.

The proxy.ts convention in Next.js is used for handling network requests, URL rewrites, and route interception before routing occurs. It replaces middleware.ts to manage network boundary tasks in Next.js 16 and above.

The proxy.ts file should be placed in the root of the src directory of your Next.js 16 project. This specific file location is required for the framework to properly intercept requests at the network boundary.

Yes, moving to proxy.ts requires adherence to specific function naming conventions for Next.js 16+. You must adjust the export function name from the previous middleware format to the new proxy standard.

You should use proxy.ts instead of middleware.ts when implementing new routing logic or migrating to Next.js 16 and above. It specifically handles URL rewrites and request interception at the network boundary before routing occurs.

Next.js 16 migration breaks middleware routing logic because the framework replaced middleware.ts with proxy.ts for network boundary tasks. Updating the file location and function naming conventions resolves the routing errors.