lynx-family/lynx-stack

Why lynx divide the render into two parts, "renderToString" and "renderOpcodeInfo"?

Open

#1,124 opened on Jun 20, 2025

View on GitHub
 (2 comments) (0 reactions) (1 assignee)TypeScript (126 forks)github user discovery
framework:Reactgood first issue

Repository metrics

Stars
 (711 stars)
PR merge metrics
 (Avg merge 3d 17h) (87 merged PRs in 30d)

Description

https://github.com/lynx-family/lynx-stack/blob/a43ae054bbe60250b0faf7a15d23b0445bb3c594/packages/react/runtime/src/lifecycle/render.ts#L29

https://github.com/lynx-family/lynx-stack/blob/a43ae054bbe60250b0faf7a15d23b0445bb3c594/packages/react/runtime/src/lifecycle/render.ts#L43

Just for SSR. But it will costs more time for traverse the vNode and optCode. Maybe make it off while CSR is better?

Contributor guide

Research direction
Investigate the reasons behind the split of render into renderToString and renderOpcodeInfo, particularly the benefits for SSR and the overhead for CSR. Consider options to conditionally skip the opcode generation during CSR.
Tech stack
typescriptreact
Domain
frontend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30