@nomiedge/registry
v0.1.1
Published
A generated, machine-readable manifest of every @nomiedge/ui component, icon, token, motion export, and chart type.
Readme
@nomiedge/registry
A generated, machine-readable manifest of every @nomiedge/ui component, @nomiedge/icons
icon, @nomiedge/tokens export, @nomiedge/motion export, and @nomiedge/charts chart type.
What this is
registry.json is generated from the real package sources — never hand-maintained. It's the
substrate the CLI (Milestone 55), templates (Milestone 56), and AI tooling (Milestone 58) all
consume: one canonical, typed description of what NDL is, instead of five different tools each
inventing their own partial version of it.
Regenerating
pnpm --filter @nomiedge/registry build:registryThis overwrites registry.json. CI regenerates it on every PR and fails if the result differs
from what's checked in — if you change a component's props or add/remove an export, regenerate
and commit the updated registry.json alongside your change.
Usage
import { loadRegistry, listByKind, getEntry } from "@nomiedge/registry";
const button = getEntry("Button"); // { kind: "component", name: "Button", props: [...], ... }
const allIcons = listByKind("icon");Adding a new entry kind
Add the shape to src/schema.ts's registryEntrySchema discriminated union, write a new
src/build/extract-<name>.ts, and call it from src/build/assemble.ts.
