@fluxfast/react

Host-independent React bindings introduced in FluxFast 1.2. These bindings are shared by the Next.js and React/Vite hosts, not a standalone HTTP server. Existing Next.js applications continue importing @fluxfast/next; that adapter re-exports the same context, components, hooks, and types.

FastAPI owns application URLs, authentication, resource loading, validation, and mutations. These bindings subscribe to @fluxfast/core; they do not introduce another router or resource cache. A host supplies SSR, the HTML document, safe serialization, hydration, assets, and same-origin transport.

Render a server-selected page

import { FluxRoot, useResource, type FluxApplicationProps } from "@fluxfast/react";

function Rooms() {
  const rooms = useResource<Array<{ id: number; name: string }>>("rooms");
  return <ul>{rooms.map(room => <li key={room.id}>{room.name}</li>)}</ul>;
}

export function Application(props: FluxApplicationProps) {
  return <FluxRoot {...props} registry={{ "rooms/index": Rooms }} />;
}

Given an envelope selecting rooms/index with a ready rooms resource, SSR renders its list. The host must hydrate from that same envelope. FluxRoot starts history, deferred work, and live subscriptions only after hydration. Unknown component identifiers fail against the explicit registry; they never become arbitrary module paths. Use Link for eligible same-origin visits, useResourceState for status/errors/staleness, useDeferredResource for deferred values and retry, useLiveStatus for connection state, and useForm for mutations and generated client validation. These retain the existing Next binding semantics.

For custom layouts, FluxProvider accepts the same envelope and registry and wraps children that use these hooks. FluxContext and useFluxContext expose the shared runtime to integration authors. Core owns navigation, caching, deferred authority, mutation patches, and live synchronization.

See the adapter contract for the host lifecycle and React API reference for the complete binding API. Application developers can use the React/Vite tutorial.

Separate @fluxfast/react/server and @fluxfast/react/client entries provide safe document SSR and exact-envelope hydration for host authors. They do not export a Vite plugin, asset server, or process supervisor; those belong to the complete @fluxfast/vite host and Python CLI. See the SSR integration reference; never import the Node server entry into browser application code.