Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
2 GitHub issues describe the same specific failure: Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
Evidence strength
- A precise single report can be well classified without proving recurrence.
- 1 dependent or duplicate group were not counted as independent confirmation.
- Stored evidence_groups are currently one bag per signal; independence is computed from logical groups.
Evidence
GitHub · vercel/next.js · Issue #96693 · Aug 4, 2026Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
Developers report that Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler.
Medium confidence based on specific workflow, specific job, specific failure, concrete reproduction, no recurrence.
With reactCompiler: true + experimental.turbopackRustReactCompiler: true, the jsx-<hash scoping class stops being added to conditionally-rendered elements inside stateful components ({expanded && <span className="fade-label"…}). In our production app we confirmed the CSS side stays hash-scoped (the rule was emitted as .animate-fadeIn.jsx-<hash while the element lacked the class), so the selector silently never match…
GitHub · vercel/next.js · Issue #96694 · Aug 5, 2026Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler
Developers report that Scoped styled-jsx loses its jsx-<hash> scoping class on conditionally-rendered elements under experimental.turbopackRustReactCompiler.
Medium confidence based on specific workflow, specific job, specific failure, concrete reproduction, no recurrence.
With reactCompiler: true + experimental.turbopackRustReactCompiler: true, the jsx-<hash scoping class stops being added to conditionally-rendered elements inside stateful components ({expanded && <span className="fade-label"…}). In our production app we confirmed the CSS side stays hash-scoped (the rule was emitted as .animate-fadeIn.jsx-<hash while the element lacked the class), so the selector silently never match…
What weakens or qualifies this
Counter-evidence has not been reviewed for this signal yet.
Timeline
- Report recorded · GitHub · vercel/next.js · Issue #96693
- Additional report · GitHub · vercel/next.js · Issue #96694
- Signal intelligence analyzed
- Published after human review
What is still unknown
- Find a second independent report.
- Collect evidence outside the current repository or community.
- Add another source platform before treating this as cross-platform recurrence.
- Confirm reports come from distinct authors when author hashes are available.
- Collect evidence across a longer observation period.
- Review maintainer responses and related reports for resolution or contradiction.
- Look for a confirmed workaround.
- Check whether the issue remains unresolved.
- Determine whether reports refer to the same incident.
How this was evaluated
Evidence support measures how strong, independent, and complete the stored evidence is for this specific problem. It separates classification quality from recurrence, keeps counter-evidence visible, and prefers “Not enough evidence yet” over a guess.
It does not measure market size, willingness to pay, competition, revenue potential, or whether anyone should build a company.
A person reviewed and published this page. Methodology: signal-intelligence-v1. Full methodology.