2.0.0-beta.30 | createStore with {ssrSource:"client"} ignores ssrSource and runs on the server

[royeden]

Describe the bug

When testing the new Solid 2.0 beta, I noticed that some browser APIs were being accessed in my async store, despite the ssrSource flag being set to 'client'.

I tried a minimal repro with console log and I can confirm this is the only primitive affected by this issue.

This only seems to happen on first load, navigating back doesn't re-trigger the server signals

Your Example Website or App

https://stackblitz.com/edit/solidjs-templates-27haqteg?file=src%2Froutes%2FHome.tsx

Steps to Reproduce the Bug or Issue

1. Open the stackblitz URL.
2. Logs should show after page load in the server console and in the client console.
3. You should see the log Log: "store" in server. No other primitive should log.

Expected behavior

I expected nothing to log on the server when the ssrSource is set to 'client'.

Screenshots or Videos

A showcase of the logs that appear on the repro

Platform

• OS: macOS
• Browser: Chrome
• Version: 150

Additional context

No response

[ryansolid]

Fixed on next (a60b288), releasing in the next beta.

Root cause: the server createStore dropped its options argument entirely when delegating the derived form to the projection machinery — so every ssrSource value was inert on the server. With "client", the server ran (and awaited) your source anyway; only the client half of the behavior worked, which is why it looked like the option was being ignored.

The options now forward through, and a hydration-parity harness scenario pins the contract: the server renders the seed without ever invoking the source (no stream hold), and the client re-derives after hydration completes.