Documentation menu

API reference

These documents describe the APIs implemented by the current source tree. They are the reference for application and tooling code. Developer internals separately contain architecture, proposals, and roadmap material that may describe APIs that do not exist yet.

Goldar is early-stage software. Every entry point is public because it is exported by the package, but not every entry point is intended for ordinary application code. The audience column makes that boundary explicit.

Entry points

ImportAudienceReference
goldarApplications; complete runtime surfaceRuntime
goldar/appApplication assembly and request hooksRuntime
goldar/adapters/cloudflareCloudflare Workers deploymentsCloudflare adapter
goldar/adapters/nodeNode.js HTTP serversNode adapter
goldar/adapters/vercelVercel Functions deploymentsVercel adapter
goldar/asyncShared MaybePromise typeRuntime
goldar/client/custom-elementsBrowser-only Custom Element registrationClient
goldar/dataRequest-scoped data resourcesRuntime
goldar/form-actionForm actions and submissionsRuntime
goldar/helpersCompatibility alias for goldar/form-actionRuntime
goldar/routerRoutes, parameters, router, and route resultsRuntime
goldar/storeRequest-scoped store base typesRuntime
goldar/viewCompiled views, rendering, and trusted HTMLRuntime
goldar/testingBlack-box request and document testsTesting
goldar/cliProject command configurationCLI
goldar/compilerLow-level compiler process and artifact modelCompiler
goldar/compiler/clientAmbient .hbs and virtual-module declarationsCompiler
goldar/compiler-runtimeGenerated-template runtime contractCompiler
goldar/viteBundled Vite integrationCompiler
goldar/typed-handlebarsProgrammatic editor toolingTyped Handlebars
goldar/language-serverEmbeddable language-server entry pointTyped Handlebars

Compiler-generated modules use goldar/compiler-runtime directly.

The template-language reference defines the implemented Handlebars subset, runtime semantics, unsupported syntax, and diagnostic codes shared by these compiler-facing entry points.

Usage guides

Current limitations

The current server runtime does not implement client navigation, browser-side stores, streaming, route-level component chunks, or nested routers. Stores and data objects are request-scoped; persistence across requests belongs in cookies, a database, or another application service. See the capability map for the boundary between implemented behavior and design direction.