AI & Agent Dev Bug Sandbox Back to Radar

Next.Js 16.4 TurbopackSharedRuntime Inlines Bootstrap Scripts Without Nonce In Prerendered Shell, Breaking Hydration Under Nonce CSP

With default experimental.turbopackSharedRuntime enabled and cacheComponents true, the prerendered shell includes inline scripts for chunk bootstrap and performance timing that lack a nonce attribute, causing browser to block them under a strict nonce-based CSP. This prevents client-side hydration and interactivity.

highConfidence 95%Next.js Affected V16.4.0

Origin Analysis

The inline scripts (from getTurbopackChunkGroupBootstrap and requestAnimationFrame timing) are rendered during static prerendering when the per-request nonce is not yet known, and are cached without a placeholder for later nonce injection. As a result, the cached shell lacks nonce attributes, and the browser blocks execution, breaking the client runtime bootstrap.

1. Clone https://github.com/stperic/next-shared-runtime-nonce-repro 2. npm install && npm run build && npm start 3. Ensure Next.js 16.4.0, Turbopack production build, cacheComponents: true, and a per-request nonce CSP via proxy/middleware (script-src 'self' 'nonce-<random>') 4. Open http://localhost:3000 5. Observe CSP violations for inline scripts without nonce and non-responsive counter button

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 workaround disables a performance optimization (shared runtime) and may increase initial script payload or reduce caching efficiency. It should be treated as a temporary mitigation. Re-enable the flag after upgrading to a fixed Next.js version and verify nonce injection works. Keep a build-time check to fail if any inline script without nonce is present to prevent regression.