Skip to content
ebitex developers

BOUNDARY_REGISTRY_SELECTOR

const BOUNDARY_REGISTRY_SELECTOR: “script[type="application/json"][data-ebitex-preview-sources]” = 'script[type="application/json"][data-ebitex-preview-sources]'

Recovering the boundary registry a server-rendered page emits.

A React page registers each boundary as it mounts, with the live `PreviewSource` the SDK handed the renderer. A server-rendered page has no such registry at runtime, so it serializes one: the two per-element attributes React already emits (`data-ebitex-source`, `data-ebitex-field`) plus a single JSON document mapping each boundary id to the same facts React holds in memory.

Keeping the per-element contract identical to React's is what allows one pin implementation (`pins.ts`) to serve both — the registry replaces the in-memory map and nothing else.