
How a Vercel CPU warning uncovered four routing bugs in my Next.js app
A Fluid Active CPU warning on Vercel sent me digging through my Next.js middleware, and I found a mis-scoped matcher burning CPU on every request, plus a routing bug that had quietly 404'd part of the app for six days.



