Skip to main content
The Reference tab carries one page per published package entry — sixteen in all — listing that entry’s runtime exports by name. The pages are generated from the packages themselves by the repository’s docs:generate script, from the same export lists the export-snapshot test pins, and a CI check fails when the committed pages differ from a fresh generation. An index therefore cannot list a symbol that does not exist, and a symbol added or removed in a release shows up here in the same change. What the index covers and what it does not:
  • Runtime exports — functions, constants and classes: everything you can import at runtime, exactly as the entry exports it.
  • Type-only exports — interfaces and type aliases such as WidgetPayload, DesignerOptions or WidgetStore are erased at build time and are not part of the index. The package READMEs and the .d.ts files in each package’s dist document them, and your editor shows them on import.
  • Signatures — the index names symbols; for parameters and return shapes read the declaration files, or the pages in this Develop tab, which describe the signatures that matter for each task.

core

@widgentic/core — every subpath below, re-exported from the root.

core/contract

Payload validation and URL guards.

core/adapters

parseJson, parseCsv.

core/mapper

inferKind, mapToWidget.

core/catalog

Catalog, built-ins, HTML serialization, hint analysis.

core/theming

Token registry, named themes, base stylesheet.

core/templates

Template DSL validation, compilation and registration.

core/actions

Action definitions, bindings, arguments, redaction.

core/reactive

mountWidget.

designer

Designers, custom elements, chrome tokens, import and export helpers.

mcp

Tool-output convention, tool definitions and handlers, app template, guarded fetch.

mcp/sdk

createWidgenticServer.

mcp/store

Store port, memory and file stores, composition, keys.

mcp/store/cosmos

createCosmosStore.

mcp/secrets

Envelope encryption and the local cipher.

mcp/secrets/keyvault

createKeyVaultCipher, kekVersionOf.
Which entry to import from is a matter of scope, not capability: the root of @widgentic/core re-exports every subpath, while @widgentic/mcp keeps its SDK, store and secrets behind their own entries so the base entry imports with no optional peer installed. Packages lists the entries with their runtimes and dependencies.