Enabling experimental.reactCompiler
causes hydration error when using styled-jsx
#65995
Labels
bug
Issue was opened via the bug report template.
Link to the code that reproduces this issue
https://github.com/marmalade-labs/react-compiler-styled-jsx
To Reproduce
bun dev
Current vs. Expected behavior
Current behavior
The styled-jsx ID is successfully rendered on the server, but it is not being rendered on the client
![image](https://private-user-images.githubusercontent.com/85196623/332195928-715c582e-6fd5-4511-a6e5-a2663ae4c082.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIwMjc5NjUsIm5iZiI6MTcyMjAyNzY2NSwicGF0aCI6Ii84NTE5NjYyMy8zMzIxOTU5MjgtNzE1YzU4MmUtNmZkNS00NTExLWE2ZTUtYTI2NjNhZTRjMDgyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDIxMDEwNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTkwYzE4YzEzOTU0MzZjMmVjMWZhNjRmOWUzYmVjMjVmM2Y3ZGVlMzY4NGVmZjVkMTg0NTExMmMzMzRlZjdlOTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.0OslmF1TVJMSl371ElDha1DHTTBJFb8OYKVAeObN0f0)
Expected behavior
The styled-jsx ID should be present in both the server and client output
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:38 +0000 Available memory (MB): 31884 Available CPU cores: 8 Binaries: Node: 18.20.2 npm: 10.8.0 Yarn: 1.22.22 pnpm: 8.15.5 Relevant Packages: next: 14.3.0-canary.72 // Latest available version is detected (14.3.0-canary.72). eslint-config-next: 14.3.0-canary.72 react: 19.0.0-rc-d3ce0d3ea9-20240520 react-dom: 19.0.0-rc-d3ce0d3ea9-20240520 typescript: 5.4.5 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local), Vercel (Deployed)
Additional context
No response
The text was updated successfully, but these errors were encountered: