Fix main-entry type re-exports failing under bundler resolution

[MaxGhenis]

Summary

Since 0.4.0, import { Badge } from "@policyengine/ui-kit" (or any other primitive/layout/chart/visualization/input/display/utils/assets symbol) fails type-check in any consumer with moduleResolution: "bundler" (Next.js, Vite, anything modern):

Type error: Module '"@policyengine/ui-kit"' has no exported member 'Badge'.

This was masked because nothing in this repo exercises the package as a consumer, and consumers were pinned at ^0.3.1 (which didn't have the conflict). Surfaced when bumping consumers to ^0.7.0 / ^0.8.0.

Root cause

The Vite multi-entry build emits dist/<name>.js and dist/<name>.cjs at the top of dist/, while tsc --emitDeclarationOnly emits dist/<name>/index.d.ts in folders. Both shapes coexist:

dist/
  index.d.ts                  <- export * from './primitives'  ← ambiguous
  primitives.js               (Vite ESM output, no types)
  primitives.cjs              (Vite CJS output, no types)
  primitives/
    index.d.ts                (tsc types, has Badge)

With moduleResolution: "bundler", TypeScript's resolution algorithm prefers the file over the folder, so ./primitives resolves to ./primitives.js (no types) and every export * silently drops the re-exported symbols. The main-entry .d.ts ends up effectively empty.

Fix

Change src/index.ts re-exports from ./<name> to ./<name>/index. tsc emits the same path verbatim into dist/index.d.ts, and the explicit folder pin forces folder resolution. Verified with a fresh tsc --noEmit against a file:-installed build of this branch:

import { Badge, Skeleton, Container, Button } from "@policyengine/ui-kit";
// ✓ no errors

Subpath imports (@policyengine/ui-kit/primitives) were unaffected — the exports map already pinned those to the index.d.ts folder path. No runtime change. Only the .d.ts re-export paths shift.

Test plan

• bun run typecheck clean
• bun run test — 26 files, 292 tests pass
• bun run build clean
• Reproduced the failure locally on 0.8.0; reproduced the fix against this branch with tsc --noEmit from a clean consumer with moduleResolution: "bundler"

Why this is urgent

Five PRs across PolicyEngine consumer repos failed CI immediately after their ^0.3.1 → ^0.8.0 bumps merged with this exact symptom (council-tax-ctr-map#1, cost-dashboard#26, economic-parameter-atlas#1, crfb-tob-impacts#116, spm-calculator#27 — all open as I file this). Once 0.9.0 ships those bumps just need a re-trigger.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
policyengine-ui-kit	Ready	Preview, Comment	May 9, 2026 1:21pm

[policyengine]

Excellent fix for a critical TypeScript resolution issue.

Analysis:
The PR correctly identifies and fixes the root cause: with moduleResolution: "bundler", TypeScript prefers files over folders when resolving paths. Since the Vite build outputs dist/primitives.js (no types) alongside dist/primitives/index.d.ts (with types), the ambiguous export * from './primitives' in src/index.ts resolves to the file, silently dropping all type exports.

The fix:
Changing all re-exports from './<name>' to './<name>/index' forces TypeScript to use folder resolution, correctly finding the .d.ts files. This is a surgical, zero-runtime-impact fix that only affects the emitted type declaration paths.

Verification:

• ✅ Typecheck passes cleanly on this branch
• ✅ The fix is minimal and precisely targeted
• ✅ Comment in src/index.ts:1 clearly explains the issue for future maintainers
• ✅ Changelog entry is comprehensive and accurate
• ✅ No changes to runtime behavior or public API surface
• ✅ Subpath imports were already correct via exports map

Impact:
This unblocks all five consumer PRs that failed with Module has no exported member errors after bumping from 0.3.1 to 0.8.0. The fix is backward-compatible and doesn't require consumer changes.

Ship it.