fix(resize-observer): keep hydration ids aligned for client-only effects

[devagrawal09]

Problem

On next, createResizeObserver and createWindowSize shift the hydration keys of every sibling rendered after them, causing hydration mismatches. For example, Kobalte Tabs.Indicator breaks hydration on direct page loads.

Cause

Solid 2 assigns hydration keys by counting owners. On the server these primitives create no owner, but on the client they do: an observer effect, and onSettled for window size.

Fix

• createResizeObserver: its client-only effect is marked { transparent: true }, so it takes no hydration ID.
• createWindowSize: calls onSettled on both sides. The server version reserves the matching ID and never runs the callback.

No extra server owners.

Why not createOwner() on the server (as #1048 did for createEventListener): these effects only exist on the client, so instead of faking an owner on the server they opt out of hydration ID counting with transparent: true. Solid documents this option as being 'for client-only effects the server never created', and it's available in the ^2.0.0-rc.14 peer range. onSettled already reserves its ID on the server, so the hydratable helpers just call it on both sides. createEventListener could adopt transparent in a follow-up for consistency.

Test

Added one hydration regression with a following sibling to the existing hydration.test.tsx. It fails before the fix.

[changeset-bot]

🦋 Changeset detected

Latest commit: 347b49d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@solid-primitives/resize-observer	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for solid-primitives-v2 ready!

Name	Link
🔨 Latest commit	347b49d
🔍 Latest deploy log	https://app.netlify.com/projects/solid-primitives-v2/deploys/6acdaeb113503ba7b2bf20c4
😎 Deploy Preview	https://deploy-preview-1069--solid-primitives-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: da755e96-4004-4855-9e4a-474a4b23963d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[devagrawal09]

Related: #1070 fixes the same owner-count issue in event-listener, interaction, keyboard, scroll, media, utils and static-store. #1071 fixes storage sync cleanup.

Release request: could you publish new next versions once these land? Two fixes are already on next but unpublished, and Solid 2 consumers need them:

• @solid-primitives/event-listener: the server owner fix from fix(event-listener): balance hydration ids for createEventListener #1048, not in 3.0.0-next.5.
• @solid-primitives/storage: the fix in 638c530 that stops persisting/broadcasting the previous value in event handlers. Its package.json is 5.0.0-next.6, but npm next is still 5.0.0-next.4.

Kobalte 2.0.0-alpha.2 pins event-listener and resize-observer exactly, so its Tabs break hydration until these ship. SolidBase is currently working around it for its Solid 2 migration (kobaltedev/solidbase#174).