Publishing a Make Kit removes component exports from the generated package entrypoint

I'm seeing an issue where publishing a Make Kit removes the component exports from the package root and creates an effectively empty JavaScript bundle. This worked in earlier versions of the kit.

EXPECTED BEHAVIOR

Components exported from src/components/index.ts should be importable from the package root after publishing.

ACTUAL BEHAVIOR

After publishing:

• dist/index.js contains only:

/* empty css */

• dist/index.d.ts contains only:

import './styles/index.css';

• Imports from the package root fail because no components are exported.

The generated src/index.ts contains only:

// Auto-generated entrypoint

import './styles/index.css';

REPRODUCTION

1. Export components from src/components/index.ts.

2. Add the following export to src/index.ts:

export * from './components';

3. Publish the Make Kit.

4. Inspect src/index.ts and the generated dist files.

5. The component export is no longer present, and the root JavaScript bundle contains no component code.

I ALSO TRIED

• Creating a separate barrel file

• Editing the exports field in package.json

These changes worked locally but were removed or reverted when the kit was published.

WORKAROUND

Configuring src/components/index.ts as an additional Vite library entry generates:

dist/components/index.js

This allows consumers to import components from the subpath.

QUESTION

Is there a supported Make Kit entrypoint convention or configuration for publishing component exports?

Or is the generated entrypoint behavior unexpected?