Upgrade to Next.js 16: Middleware Renamed to Proxy.tsUpgrade to Next.js 16: Middleware Renamed to Proxy.ts
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Husnain's avatar
Husnain Ali
• Feb 21
Next.js 16 renamed middleware.ts to proxy.ts
If you're planning to upgrade to Next.js 16, heads up.
middleware.ts is now proxy.ts.
The Next.js team renamed it to better describe what it actually does. It sits at the network boundary and intercepts requests before they reach your app.
It also runs on Node.js runtime now, not Edge.
The migration is simple: → Rename middleware.ts to proxy.ts → Rename your exported function to proxy → Your logic stays the same
middleware.ts still works for now but it's deprecated and will be removed in a future version
Small change, easy to miss. Just wanted to put it on your radar
More details here: https://nextjs.org/blog/next-16

nextjs.org

Next.js 16

Next.js 16 includes Cache Components, stable Turbopack, file system caching, React Compiler support, smarter routing, new caching APIs, and React 19.2 features.

Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started