AI & Agent Dev Bug Sandbox Back to Radar

Streaming Metadata Wrapper Uses <Div> Causing Hydration Deletion When Third-Party Prepends Same Tag

Next.js Streaming Metadata renders a <div hidden> as the first child of <body>. React 19 hydration matches only by tag name and claims any prepended <div> (e.g. consent manager or chat widget) as the metadata wrapper. Hydration then fails with Minified React error #418, and React's clearContainerSparingly removes the third-party DOM node.

highConfidence 95%Next.js Affected V16.3.4 Affected V16.4.0-Canary.25

Origin Analysis

Next.js's MetadataWrapper in packages/next/src/lib/metadata/metadata.tsx uses a plain <div> as the host element for streaming metadata. React 19's canHydrateInstance skips foreign nodes only when the tag name differs. Because <div> is the most common tag prepended by third-party scripts before hydration, the wrapper collides with those nodes, causing hydration mismatch and deletion.

1. Create an App Router project with streaming metadata (default).\n2. In app/page.tsx add an inline script that prepends <div id="third-party"> to document.body during HTML parsing.\n3. Build and start the app, open the page with console open.\n4. Observe Minified React error #418 and that #third-party is removed from the DOM.\n5. Change the prepended tag from 'div' to 'aside' and repeat; no error occurs and the node is kept.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change alters the server-rendered HTML from <div hidden> to <next-metadata hidden>. Ensure the custom element is recognized by TypeScript JSX (Next.js already supports similar tags like <next-route-announcer>). Test in all supported browsers; while custom elements are widely supported, legacy browsers or strict HTML parsers may treat it differently. If the custom element introduces any styling or hydration edge case, rollback by reverting to <div> and consider a different mitigation such as rendering metadata outside <body> or using a more unique standard element. No concurrency or multi-thread issue is introduced; the race condition remains but is made harmless.