Affected version
Reports that share this version, grouped in one feed.
Next.js App Router with Edge SSR streaming defers metadata into Suspense chunks. Bots like TelegramBot, ChatGPT-User, GPTBot, and ClaudeBot terminate the response after the initial HTML chunk, causing empty social cards and missing SEO metadata.
Next.js App Router does not emit `<link rel="preload" as="style">` hints before blocking stylesheets in the initial HTML, forcing the browser preload scanner to wait until the parser encounters each `<link rel="stylesheet">`, which delays FCP.
In Next.js 16.3.5-16.4.0-canary.32, a redirect() inside a Suspense boundary in a layout triggers an instant navigation validation error on every warm request, although redirect is intentional control flow. This suppresses genuine blocking-prerender-dynamic findings on the same route.