API Reference
The v0.44.0-beta.1 current line documents only the five consumer packages. Retired alpha packages and internal subpaths are not authoring surfaces.
Authoring starts at product packages.
Five products, one application path.
The supported Custom Element authoring surface for JSX, DSD, hydration, signals and styles.
Start here for standalone element authoring.Author compiled elements as `@element`-decorated `OpenElement` classes with `@property` state; `StyleSheet` and signal helpers come from the same root.@experimental additions: the `element`/`property` decorator intrinsics (#1209) and the dangerous-key guards `isDangerousKey`, `injectPropsSafe`, `DANGEROUS_KEYS` (#1214).The application surface for pages, routes, islands and request/render semantics.
Use `definePage`, `defineIslandConfig` and `defineApp` for application authoring.The router and request-driver implementation are internal product knowledge.The official Vite, content, static-build and Nitro output adapter.
Use `buildApp()` or the generated build task.Plugin ordering, manifests and content scans are adapter implementation details.The installed starter and zero-context consumer entrypoint.
Generated projects expose `dev`, `check`, `test`, `build`, `start` and `preview`.The starter imports product packages only.Optional primitives retained only when they have demonstrated reusable behavior.
UI is not required to use OpenElement.Website-specific brand, hero, lab and layout artifacts are not UI package contracts.