Universal apps

Server-side rendering is usually sold as a special build with its own rules. Under the Continuum it is something simpler and stranger: the same pages, resolved by two contexts, one after the other. Once you see it that way, hydration stops being magic.

#SSR is a superposition

import { StoneApp } from '@stone-js/core'
import { Routing } from '@stone-js/router'
import { UseReact } from '@stone-js/use-react'
import { Browser } from '@stone-js/browser-adapter'
import { NodeHttp } from '@stone-js/node-http-adapter'

@Browser()    // resolve in the browser (hydration, client nav)
@NodeHttp()   // ...and on the server (first paint)
@UseReact()
@Routing()
@StoneApp()
export class Application {}

import { defineStoneApp } from '@stone-js/core'
import { routerBlueprint } from '@stone-js/router'
import { useReactBlueprint } from '@stone-js/use-react'
import { browserAdapterBlueprint } from '@stone-js/browser-adapter'
import { nodeHttpAdapterBlueprint } from '@stone-js/node-http-adapter'

export const App = defineStoneApp(
  { name: 'tasks-ui' },
  [routerBlueprint, useReactBlueprint, browserAdapterBlueprint, nodeHttpAdapterBlueprint]
)

#Why this is more than a trick

Because both resolutions run the same domain, there is no separate server codebase to keep in sync with the client. A loader that fills a page on the server is the same loader that fills it on a client navigation. The seam between server and browser, the usual source of universal-app bugs, is gone by construction.