You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
refactor(mosaic): split compound components into client leaves and namespace parts - #10795
Stacked on #10754. Prepares compound components for React Server Components; #10806 builds on this to make them render from RSC.
Each of the 25 compound components now follows the Base UI layout:
<name>.tsx is a 'use client' leaf with prefixed exports (PanelRoot, PanelTitle, ...).
<name>.parts.ts re-exports them under the part names (Root, Title, ...).
index.ts does export * as Panel from './panel.parts'.
The 7 published compound indexes (avatar, banner, data-list, empty-state, entity, item, table) keep 'use client', so published behavior is unchanged. X.Part usage and the XProps types are unchanged. Each compound is now a module namespace object instead of a plain object, so its parts are read-only.
Other changes:
Panel.Title passes [ref, panelTitleRef] to useRender instead of a conditional ref. The forward-ref-parts rule now checks it because it is exported, and it could not trace the conditional. Behavior is unchanged: the old ref was only null inside a profile page, where enabled is false and useRender returns null without rendering an element.
Checklist
pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
No actionable comments were generated in the recent review.
Walkthrough
Mosaic compound components now export their parts as individually named components and expose short part aliases through package-level namespaces. Component modules add the use client directive, and tests import components through their package entry points. The PanelTitle ref handling and the Profile ResizeObserver test double also change. The added changeset file contains only front-matter delimiters.
This refactor restructures how compound components are exported while keeping the public namespace usage (such as Panel.Title) and prop types unchanged. No concrete defect was found, so it looks ready to merge after the normal build and test checks.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title names the main change: the 25 compound components are split into 'use client' leaf files and namespace part exports. The changeset matches this. The title is specific, follows the convention…
Description check
The description states that the change stacks on #10754 and prepares compound components for React Server Components. It explains the new file layout (client leaf, parts re-export, namespace index), t…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names the main change: the 25 compound components are split into 'use client' leaf files and namespace part exports. The changeset matches this. The title is specific, follows the conventional commit format, and does not describe anything absent from the changeset.
Full details: Description check
Explanation
The description states that the change stacks on #10754 and prepares compound components for React Server Components. It explains the new file layout (client leaf, parts re-export, namespace index), the seven published indexes that keep 'use client', and the Panel.Title ref change. All of this matches the changeset.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.
All 7 published entries still start with 'use client', and a Server Component page using the compounds fails the same way before and after, so published behavior is unchanged.
Merge-base
This PR 89199fa6
Merge-base
This PR 89199fa6
Also checked · 2 match · 1 not run
Panel.Title refs unchanged · Skipped Client Component usage unchanged Compound parts are now read-only
Proof on 89199fa6 · Did Proof get it right? Yes · No
alexcarpenter
changed the title
feat(mosaic): render compound components from Server Components
refactor(mosaic): split compound components into client leaves and namespace parts
Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Stacked on #10754. Prepares compound components for React Server Components; #10806 builds on this to make them render from RSC.
Each of the 25 compound components now follows the Base UI layout:
<name>.tsxis a'use client'leaf with prefixed exports (PanelRoot,PanelTitle, ...).<name>.parts.tsre-exports them under the part names (Root,Title, ...).index.tsdoesexport * as Panel from './panel.parts'.The 7 published compound indexes (
avatar,banner,data-list,empty-state,entity,item,table) keep'use client', so published behavior is unchanged.X.Partusage and theXPropstypes are unchanged. Each compound is now a module namespace object instead of a plain object, so its parts are read-only.Other changes:
Panel.Titlepasses[ref, panelTitleRef]touseRenderinstead of a conditional ref. Theforward-ref-partsrule now checks it because it is exported, and it could not trace the conditional. Behavior is unchanged: the old ref was onlynullinside a profile page, whereenabledis false anduseRenderreturnsnullwithout rendering an element.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change