Skip to main content
widgentic ships as three npm packages under the @widgentic scope. All three are ES modules only, publish compiled JavaScript with TypeScript declarations and source maps under dist, and are released by the repository’s workflow with an npm provenance attestation — never from a developer machine. They are versioned as a linked group: packages released together take the same version, so a release never leaves two of them on confusingly adjacent numbers. A package with no changes in a release keeps its version, so the three numbers can differ — install the latest of each. Every entry below is a subpath in the package’s exports map, resolving for both the types and the default import condition. The linked pages list each entry’s runtime exports; they are generated from the packages themselves (see API reference).

​
@widgentic/core

The engine: definitions, validation and rendering only — no designer, server or persistence code, and no Node-only modules (no node: imports, no Buffer, no process), so it runs in browsers and in Node alike. It declares no dependencies and no peer dependencies.

​
@widgentic/designer

The hostable designers as factories and opt-in custom elements. Browser only; depends on @widgentic/core and nothing else. One entry: designer. For pages without a bundler the package also publishes a single-file ES module bundle with core inlined at dist/browser/widgentic-designer.js (declared as the ./browser subpath). Loading it from a module script registers the designer elements, so <widgentic-designer> mounts without any other network request for widgentic code. The module build stays the primary entry for bundler users. See Embed the designers.

​
@widgentic/mcp

Requires Node 22 or later (it relies on net.BlockList, AbortSignal.timeout and the global fetch). Depends on @widgentic/core. Its other dependencies are optional peers, needed only by the entry that imports them: The base entry and ./store import with none of the peers installed. To run a server, install the SDK peers alongside:
Install the Azure clients only if you import the Cosmos or Key Vault entries. See Run your own server.

​
What a tarball contains

Each package publishes dist/**, package.json, README.md and LICENSE (MIT) — no TypeScript sources, tests or fixtures — with sideEffects: false, an engines.node range and a repository field pointing at the public repository. The declarations type-check under Node16 and bundler module resolution. Type-only exports (interfaces and type aliases) are not part of the generated export index; the package READMEs and the .d.ts files cover them.