Would love to generally see SSR supported in Storybook. Just started up Storybook in a Remix codebase and would love to see SSR'd vs Client Rendered components.

Not too familiar with React server components, so I have a question.

Are you implying that a client rendered component can be different from a server rendered one? I always assumed this was just implementation details for the same result.

They can be different in that server rendered ones are materialized solely on the server, without any context to the browser environment and unable to have any interactivity. It's just HTML when it's SSR'd. However, when "hydrated" or when that component is rendered on the client (browser), it can ship with more interactivity and/or manipulation by its JS.

I saw a company using it with their homemade php backend/components.

We tried using this in a small/medium business and it was too cumbersome.

This probably works best in very slow-moving enterprises with questionable developers.

Using storybook? Or SSR? Honestly neither makes sense to me in the context of your observation but I'd like to at least know which to ask more about. Can you expand?

Agree, storybook has too many little issues and slows down smaller projects. I too feel it’s ideal for larger, slow moving projects.

tl;dr: Significant upgrade to Storybook’s support for the latest changes in React/Next, which lets you bring RSCs into Storybook (by rendering RSCs in the client)! Available to try now in the first SB 8.0 alpha. Much more to come as part of the 8.0 launch in months ahead!