Why lynx divide the render into two parts, "renderToString" and "renderOpcodeInfo"? · lynx-family/lynx-stack

(2 条评论) (0 个反应) (1 位负责人)TypeScript (135 个派生)github user discovery

framework:Reactgood first issue

仓库指标

星标: (730 个星标)
PR 合并指标: (平均合并 3天 17小时) (30 天内合并 87 个 PR)

描述

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?

贡献者指南

研究方向: 调查将渲染拆分为 renderToString 和 renderOpcodeInfo 的原因，特别是对 SSR 的好处以及对 CSR 的额外开销。考虑在 CSR 时有条件地跳过操作码生成的选项。
技术栈: typescriptreact
领域: frontend
议题类型: 调研
难度: 3
预计时间: 半天
活动状态: 活跃
清晰度: 清晰
前置要求: ReactTypeScript
新手友好度: 30