AI & Agent Dev Bug Sandbox Back to Radar

React Compiler + Turbopack: Browser Source Map `SourcesContent` Is The Compiler Output (Wrong Line Numbers) For Client→Client Imports

When React Compiler is enabled with Turbopack and production browser source maps, client components imported by other client components generate source maps where `sourcesContent` is the compiler output instead of the original source, causing incorrect line numbers and breaking devtools and error tracking tools.

highConfidence 85%Next.js Affected V16.2.6 Affected V16.3.0-Canary.40

Origin Analysis

Turbopack's source map generation for client-to-client imports incorrectly uses the React Compiler's transformed output as the `sourcesContent` instead of chaining the compiler's source map back to the original source file. This happens only when a client component imports another client component, indicating that the source map chain is not correctly applied in that specific module graph path.

1. Clone and install: git clone https://github.com/atkaiser/rc-sourcemap-repro && cd rc-sourcemap-repro && npm install 2. Run npm run build to build with React Compiler enabled. 3. Run npm run inspect to inspect the browser source map. Observe `sourcesContent` for `app/widget.tsx` is 27 lines with compiler runtime imports. 4. Run npm run build:no-rc to build with React Compiler disabled (REACT_COMPILER=false). 5. Run npm run inspect again. Now `sourcesContent` is 9 lines identical to the real file.

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 fix forces `sourcesContent` to be read from disk, which may add I/O overhead during build and could fail if source files are virtual or generated. Additionally, it may mask legitimate source map transformations from other plugins. Rollback: remove the post-processing function and rely on the original Turbopack source map generation. Test with various transforms (Babel, SWC, custom loaders) to ensure no regressions.