@lemonadejs/calendar 5.9.0 → 5.9.1

package/dist/react.d.ts

@@ -41,15 +41,33 @@ declare namespace CalendarReact {
         style?: React.CSSProperties;
         children?: React.ReactNode;
     }
+
+    /**
+     * Re-export the underlying type namespace so consumers can write
+     *   import { Calendar } from '@lemonadejs/calendar/react';
+     *   import type { Calendar as CalendarNS } from '@lemonadejs/calendar/react';
+     * and get `CalendarNS.Options`, `CalendarNS.Instance`, etc. The same
+     * applies through the `@calendarjs/react` aggregate.
+     */
+    export type Options = Calendar.Options;
+    export type Instance = Calendar.Instance;
+    export type ValidRange = Calendar.ValidRange;
+    export type ValidRangeItem = Calendar.ValidRangeItem;
+    export type CloseOptions = Calendar.CloseOptions;
 }
 
-declare const CalendarReact: React.MemoExoticComponent<
+// Interface (not const) so the value type declaration-merges with the
+// namespace above. That merge carries the type members along with the
+// React component value when the default export is re-exported.
+interface CalendarReact extends React.MemoExoticComponent<
     React.ForwardRefExoticComponent<
         Omit<Calendar.Options, 'onchange' | 'onupdate' | 'onclose' | 'onopen' | 'onChange'>
         & CalendarReact.ReactCallbacks
         & CalendarReact.DOMProps
         & React.RefAttributes<Calendar.Instance>
     >
->;
+> {}
+
+declare const CalendarReact: CalendarReact;
 
 export default CalendarReact;

package/package.json

@@ -36,5 +36,5 @@
         "./style.css": "./dist/style.css",
         "./dist/*": "./dist/*"
     },
-    "version": "5.9.0"
+    "version": "5.9.1"
 }