[Bug] swizzle generates a BaseProps subpath import that is not exported

[is0060hf]

Description

astryx swizzle Button generates this type import:

import type {BaseProps} from '@astryxdesign/core/BaseProps';

However, @astryxdesign/core does not define ./BaseProps in its package.json exports. Node package resolution reports ERR_PACKAGE_PATH_NOT_EXPORTED, and TypeScript reports TS2307.

The generated source should import BaseProps through a public package export. This could be addressed either by changing the swizzle import rewrite or by exporting the ./BaseProps subpath.

Reproduction

1. Create a fresh Next.js 16 application.

2. Install Astryx v0.1.6.

3. Run:

   astryx swizzle Button

4. Inspect the generated Button source. It imports BaseProps from @astryxdesign/core/BaseProps.

5. Run TypeScript. It reports TS2307 because that subpath is not exported.

The same result was reproduced with v0.1.4.

Workaround

Change only the generated import to the package barrel:

import type {BaseProps} from '@astryxdesign/core';

After this one-line change, TypeScript exits with code 0. The import is type-only, so this workaround does not change runtime behavior.

Astryx Version

@astryxdesign/core@0.1.4 and @astryxdesign/core@0.1.6

Environment

Fresh Next.js 16 application

[Rinielg]

Confirming this still reproduces on @astryxdesign/core@0.1.8 / @astryxdesign/cli@0.1.8 (reported here against 0.1.4 and 0.1.6).

astryx swizzle Button --output ./src/swizzled rewrites 11 imports. 10 resolve; only ./BaseProps does not:

✔ @astryxdesign/core/utils
✔ @astryxdesign/core/Tooltip
✔ @astryxdesign/core/theme
✔ @astryxdesign/core/Spinner
✔ @astryxdesign/core/VisuallyHidden
✔ @astryxdesign/core/Layout
✔ @astryxdesign/core/SizeContext
✔ @astryxdesign/core/ButtonGroup
✔ @astryxdesign/core/Link
✗ @astryxdesign/core/BaseProps   ERR_PACKAGE_PATH_NOT_EXPORTED

So the import-rewrite table looks correct for every subpath except this one, which suggests the fix is a single missing "./BaseProps" entry in the exports map (or rewriting that one specifier to the barrel).

The workaround in the original report holds — import type {BaseProps} from '@astryxdesign/core'; — and since it is type-only, runtime behaviour is unchanged. tsc --noEmit then passes on the swizzled 825-line component under strict + noUncheckedIndexedAccess.

Worth noting for anyone hitting this: the failure is silent at swizzle time. The CLI reports success and the broken import only surfaces on the next typecheck or build.