Server-Side Rendering (SSR)

[jheer]

Thanks for the great work on Framework!

For even faster (perceived) page loads it would be valuable to render initial views of charts and other content on the server, then "hydrate" them on the client once corresponding runtime cells are ready. For example, I'd like to publish static SVG as part of the initial page content, which can then be replaced with "live" content upon load.

I realize there be dragons here, especially with arbitrary code that may involve randomness, generators, or otherwise cause strange changes of content upon hydration, and so on. Nevertheless, I see a lot of value in being able to knowingly opt-in to SSR.

I imagine one would have to instantiate a runtime during server-side compilation then extract resulting content. We do something similar in Living Papers using Puppeteer to extract and screenshot runtime-generated content, though a lighter weight approach (e.g., using jsdom and node canvas?) may be preferable and cover common use cases.

It looks like some work in this direction is ongoing, though I'm not sure of the planned scope. So, just wanted to share a plug for this!

[mbostock]

Related #234 #141.

[Fil]

As a complement/alternative/easy first step, I would like to think about registering cell dimensions #933.

[jaanli]

Agreed! This would support very cool use cases, added a discussion as well:

#855

[Fil]

Maybe we should reopen this issue, which is mentioned in

framework/docs/jsx.md

Line 114 in fa80489

In the future we intend to support other JSX-compatible frameworks, such as Preact. We are also working on server-side rendering with client-side hydration; please upvote [#931](https://github.com/observablehq/framework/issues/931) if you are interested in this feature.

and not completely completed? Or open a new one with new goals (SSR code blocks, hydration…).

[mbostock]

We have #234 #145 already so let’s keep this closed. We could open up another issue for JSX hydration.