Supported product
@openelement/element
4 entriesThe supported Custom Element authoring surface for JSX, DSD, hydration, signals and styles.
@openelement/element- Supported entries: root, jsx-runtime, jsx-dev-runtime, build-utils
- Start here for standalone element authoring.
- Use `defineElement`, `OpenElement`, `StyleSheet` and signal helpers without importing renderer internals.
Supported product
@openelement/app
5 entriesThe application surface for pages, routes, islands and request/render semantics.
@openelement/app- Supported entries: root, hono, model, spa, preact
- Use `definePage`, `defineIsland` and `defineApp` for application authoring.
- The router and request-driver implementation are internal product knowledge.
Supported product
@openelement/adapter-vite
4 entriesThe official Vite, content, static-build and Nitro output adapter.
@openelement/adapter-vite- Supported entries: root, nitro-mount, cli/build, sitemap
- Use `buildApp()` or the generated build task.
- Plugin ordering, manifests and content scans are adapter implementation details.
Supported product
@openelement/create
1 entriesThe installed starter and zero-context consumer entrypoint.
npm:@openelement/create- Supported entries: CLI binary
- Generated projects expose `dev`, `check`, `test`, `build` and `preview`.
- The starter imports product packages only.
Supported product
@openelement/ui (optional)
2 entriesOptional primitives retained only when they have demonstrated reusable behavior.
@openelement/ui- Supported entries: root, retained primitive subpaths
- UI is not required to use OpenElement.
- Website-specific brand, hero, lab and layout artifacts are not UI package contracts.