4 posts tagged this topic.
Next.js 16 removed the 'eslint' key from its config type, and a key written into next.config.ts anyway didn't fail at runtime — it failed the type checker. The CI gate sat red for about a week before anyone acted on it, and the first to act was a baseline audit, not anyone watching the build.
A Google Reviews listing-confirm route taught me that 'it saved' and 'everything it triggered afterward also worked' are two different claims, and a response body should never merge them into one.
AIDA's public intake route checks content length, per-file size, a running total, and byte-sniffed MIME type before saving an attachment. None of that mattered once Next.js's own proxy layer silently truncated the request body first, with no error back to the client.
An AI agent blamed a failing Playwright test on Next.js response caching. I traced the code and blamed middleware. We were both wrong about the observation: the test's "anonymous" context was quietly authenticated. Two stacked bugs, two confident stories, and the re-run as the only reviewer that counted.