Radix components emit Emotion first-child SSR errors on every dev page load

Open
#7,098 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
frontend, web-dev

Research direction

Start with the reproduction artifacts in results/out_dev/radix.json and results/out_base/radix.json, then read finding 034-03 in the linked campaign report and cluster notes. Trace how the Radix components are included in the dev SSR path and confirm the three Emotion errors are no longer emitted on /radix while production behavior remains unchanged.

Written by the indexing model from the issue text.

Description

Every dev load of /radix logs three
The pseudo class ":first-child" is potentially unsafe when doing server-side rendering. Try changing it to ":first-of-type".
errors (console level error, not warning). Identical count on 0.9.10.post2; absent in prod.
Evidence: results/out_dev/radix.json, results/out_base/radix.json.

Source: prerelease finding 034-03, recorded against Reflex 0.9.11a1 and compared with 0.9.10.post2. See the full campaign report and cluster notes and reproduction artifacts. Findings and verification status above are from that campaign; this filing does not claim a new browser rerun.

Dominant language
Python
Stars
28.9k
Forks
1.8k
Avg merge
1d 20h
Merged PRs (30d)
173

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reflex-dev/reflex

All issues in reflex-dev/reflex

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.