Next 16 renamed middleware to proxy, and our whole auth boundary is one allowlist
I have been building Nakodo, a field guide to YouTube creators: it reads a brand's website, searches YouTube for creators who fit, collects the contact details those creators publish, and drafts a first message. It runs on Next 16.3.7 with Supabase for auth. The first thing that surprised me on this build was that middleware.ts no longer exists. The file is src/proxy.ts and the named export is proxy. From the Next 16 docs shipped in the package: Starting with Next.js 16, Middleware is now called Proxy to better reflect its purpose.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in