API reference
TypeDoc generates this reference from every current export in package-contract.json. The build fails when generation emits a warning, when the documented entry-point count differs from the public package contract, or when an internal link is broken.
New to Gluon? Start with Components: properties, events, and lifecycle before using the signature reference. Its class map explains which public class to construct, subclass, receive as an error, or reserve for tooling.
Use the package portal to compare every current package's purpose, runtime, installation command, peers, public exports, and supported scope before opening generated symbol documentation.
See the accessibility and compatibility support matrix for the evidence boundary shared by the package portal and release line.
Runtime
@gluonjs/core@gluonjs/core/styles@gluonjs/core/analytics@gluonjs/reactivity@gluonjs/router@gluonjs/router/memory@gluonjs/store@gluonjs/i18n
Universal rendering
Tooling
@gluonjs/compiler@gluonjs/compiler/diagnostics@gluonjs/vite@gluonjs/gluon-components-vite@gluonjs/test-utils@gluonjs/devtools-api@gluonjs/devtools@gluonjs/language-servercreate-gluon
Optional UI packages
Each package exports a machine-readable stable-contract manifest. The compiled interactive UI example exercises themes, controls, compositions, and headless listbox keyboard behavior.