May 2026 - Registry Include and Validate

This release adds two updates for registry authors:

• include for composing large source registries from multiple registry.json files.
• JGuang UI Registry for checking source registries before publishing.

This makes it easier to maintain source and dynamic registries without keeping one large registry.json file by hand.

Registry authors can now organize a large source registry across multiple registry.json files and compose them with JGuang UI Registry.

registry.json
components
└── ui
    ├── button.tsx
    ├── input.tsx
    └── registry.json
hooks
├── registry.json
├── use-media-query.ts
└── use-toggle.ts

{/* prettier-ignore */}

Use the JGuang UI Registry URL provided on /systems/jguang-ui#install.

Included registry.json files are valid registry files for composition and may omit name and homepage. Only the root registry.json must define the registry metadata.

Use the JGuang UI Registry URL provided on /systems/jguang-ui#install.

Build output

JGuang UI Registry resolves included registries and writes a flattened registry.json without include. Item file paths are preserved from the root registry, so a file declared in components/ui/registry.json is written as components/ui/button.tsx in the built registry item.

Validate your registry

You can now validate a source registry before publishing or serving it.

Use the JGuang UI Registry URL provided on /systems/jguang-ui#install.

Validation runs against the source registry files directly. You do not need to run JGuang UI Registry first.

The command checks the root registry.json, included registry files, item schema errors, duplicate item names, include rules, and local item file paths. Validation reports all actionable errors it can find in one run.

Registry loaders

The JGuang UI Registry package also exports loadRegistry and loadRegistryItem for dynamic registry routes.

Use the JGuang UI Registry URL provided on /systems/jguang-ui#install.

Use the JGuang UI Registry URL provided on /systems/jguang-ui#install.

See the registry.json documentation and getting started guide for more details.