Package entry points
Import the capabilities your app needs. Optional tools have dedicated entries, and the reactivity entry works without a DOM.
Import map
Section titled “Import map”| Entry | Includes |
|---|---|
@jnreis/briojs | App, components, DOM enhancement, trusted HTML, and core types. |
@jnreis/briojs/reactivity | DOM-independent state, signals, effects, computed values, batching, async resources, and scopes. |
@jnreis/briojs/persistence | Local/session/custom storage, with scope cleanup where owned. |
@jnreis/briojs/router | Optional history or hash router. |
@jnreis/briojs/http | Fetch helpers and HttpError. |
@jnreis/briojs/forms | Validation rules and validate. |
@jnreis/briojs/step | Step navigation. |
@jnreis/briojs/money-mask | Optional moneyMask formatter. |
@jnreis/briojs/devtools | Development-only instrumentation and inspector panel. |
@jnreis/briojs/astro | Optional named-island lifecycle integration and lazy code loading. |
@jnreis/briojs/dist/* | Built files for self-hosted standalone browser scripts. |
Runtime and browser requirements
Section titled “Runtime and browser requirements”All JavaScript entry points are ES modules; there is no CommonJS build. Runtime dependencies are not required. Brio enhances client-rendered DOM rather than providing server-side rendering or hydration of framework-generated server output. Its reactivity entry can run without a DOM. Modern browsers are required; optional observer directives and native CSS features depend on browser support.
References for older applications
Section titled “References for older applications”For a private application built with an older Brio runtime, use the legacy migration kit. The historical v3 reference is preserved in the repository, not shipped as current documentation.