fix: generate chart component registry

[awhobbs87]

Summary

Fixes missing API reference tables for chart components, including BubbleMap and ChoroplethMap, on the maps documentation page.

Changes

• Discover components exported from multi-component barrel directories when matching props types are exported.
• Categorize chart entries under Data Visualization.
• Extract complete props metadata and JSDoc descriptions from generic interfaces when schema generation cannot process the root type.
• Add regression coverage for barrel discovery and generic interface extraction.
• Add a patch changeset for @cloudflare/kumo.

Validation

• pnpm --filter @cloudflare/kumo test:unit --run scripts/component-registry/index.test.ts

• pnpm --filter @cloudflare/kumo typecheck

• pnpm --filter @cloudflare/kumo lint

• pnpm --filter @cloudflare/kumo build

• pnpm --filter @cloudflare/kumo-docs-astro build

• Verified /charts/maps/ renders both API tables without registry error banners.

• Reviews

  • bonk has reviewed the change
  • automated review not possible because: registry generation and static documentation output require repository build context

• Tests

  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:

[geoquant]

/bonk review

[pkg-pr-new]

npm i https://pkg.pr.new/@cloudflare/kumo@624

commit: dcfc830

[github-actions]

Docs Preview

View docs preview

Commit: dcfc830

[ask-bonk]

This is a clean, targeted fix. The barrel-directory discovery logic correctly identifies components that previously fell through the conventional {dir}/{dir}.tsx pattern, and the generic-interface fallback in generatePropsFromType provides meaningful props metadata when ts-json-schema-generator cannot process the root type. The test coverage for both paths looks good.

Left a few minor inline notes — none are blockers.

[ask-bonk]

Review posted successfully on PR #624. I left a batch review with three minor inline suggestions (none blocking):

• discovery.ts: Consider a .ts fallback when resolving barrel source files.
• sub-components.ts: The generic-interface regex may struggle with nested object-literal generics.
• index.ts: The readFileSync inside the catch block isn't guarded against read errors.

Overall the PR is clean and well-tested.

github run

[awhobbs87]

/bonk review

[mattrothenberg]

/bonk please re-review

[ask-bonk]

All previous review feedback has been addressed cleanly:

1. Barrel resolution — detectComponentExportsFromIndex now checks both .tsx and .ts extensions, with test coverage for plain TypeScript modules.
2. Generic interface extraction — extractPropsFromInterface was rewritten to use the TypeScript AST instead of regex, correctly handling nested generic constraints and object-literal prop types.
3. Guarded fallback reads — readFileSync inside the generatePropsFromType catch block is now wrapped in its own try/catch, preserving the variants-only fallback if source reading fails.

The barrel-directory discovery correctly avoids double-processing directories that already have a conventional {dir}/{dir}.tsx entry point, and the category addition for chart is straightforward. Tests pass and the change is well-scoped. LGTM.

[ask-bonk]

Review posted successfully on PR #624. Approved.

github run

[github-actions]

Visual Regression Report — 1 changed, 0 unchanged

1 screenshot(s) with visual changes:

Sidebar

387 px (0.03%) changed

Before	After	Diff

---

Generated by Kumo Visual Regression