Skip to content

Commit 85e0733

Browse files
committed
fix: force NavigationNavbar and NavigationItem into published d.ts
NavigationItem (and NavigationNavbar's own declaration) reached the root barrel only through `export * from './custom'`, which rollup-plugin-dts drops from the bundled d.ts - so `import { type NavigationItem } from '@sistent/sistent'` failed type-checking downstream despite the runtime export existing. Add an explicit root re-export following the established FeedbackButton pattern to force both declarations into the published bundle. Signed-off-by: marblom007 <[email protected]>
1 parent e6a8fc9 commit 85e0733

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

‎src/index.tsx‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,14 @@ export {
4848

4949
export { DataTableToolbar, type DataTableToolbarProps } from './custom/DataTableToolbar';
5050

51+
// Same nested-barrel dts-drop quirk as FeedbackButton above: reaching the entry
52+
// only through `export * from './custom'`, rollup-plugin-dts drops both the
53+
// `NavigationNavbar` component declaration and the `NavigationItem` type from the
54+
// bundled d.ts, so `import { NavigationNavbar, type NavigationItem } from
55+
// "@sistent/sistent"` fails type-checking despite the runtime exports existing.
56+
// The explicit re-export forces both declarations into the published bundle.
57+
export { NavigationNavbar, type NavigationItem } from './custom/NavigationNavbar';
58+
5159
// Same nested-barrel dts-drop quirk as FeedbackButton above. `createCanShow` is
5260
// worse than a missing type: consumers still resolve it at runtime, so the import
5361
// silently degrades to `any` and its `eventBus` argument stops being

0 commit comments

Comments
 (0)