React workspaces and browser clients
React workspaces and browser clients
Section titled “React workspaces and browser clients”Elevator Pitch
Section titled “Elevator Pitch”Application authors use React workspaces and portable clients to bind authenticated product UI.
Why & Value
Section titled “Why & Value”Definitions carry domain fields and commands while shared components handle presentation and session changes. Live backend checks remain mandatory. This MIT package owns its implementation and declarations in the public monorepo.
Key Highlights
Section titled “Key Highlights”- Definition-driven workspaces
- Session-bound execution
- Browser Worker computation
- Shared help
Quickstart
Section titled “Quickstart”Registry installation requires a published release. During pre-publication development, install the checksum-pinned tarballs produced by the workspace build instead of assuming these names exist in a registry.
Public import
Section titled “Public import”Install the owning package and use the exact import in the example below. The subpath is not a separate npm package. Check the selected entry’s runtime and peer requirements in the linked architecture guide.
bun add @alneas/eaos-reactimport { titleRecordSchema } from '@alneas/eaos-react/record-workspace'
const schema = titleRecordSchema({ type: 'object', properties: { title: { type: 'string' } },}, { title: 'Title' })console.log(schema.properties.title.title)