@umituz/react-native-onboarding 1.0.2 → 1.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umituz/react-native-onboarding",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Generic onboarding flow for React Native apps with gradient backgrounds, animations, and customizable slides. SOLID, DRY, KISS principles applied.",
   "main": "./src/index.ts",
   "types": "./src/index.ts",

package/src/index.ts

@@ -55,10 +55,15 @@ export { OnboardingHeader, type OnboardingHeaderProps } from "./presentation/com
 export { OnboardingFooter, type OnboardingFooterProps } from "./presentation/components/OnboardingFooter";
 
 // Export OnboardingSlide component
-// Note: We export it with the same name as the type, which TypeScript allows
-// because one is a type (from domain) and one is a value (component)
-// Users can import both: 
-//   import type { OnboardingSlide } from '@umituz/react-native-onboarding'; // type
-//   import { OnboardingSlide } from '@umituz/react-native-onboarding'; // component
-export { OnboardingSlide, type OnboardingSlideProps } from "./presentation/components/OnboardingSlide";
+// Note: TypeScript doesn't allow exporting both a type and a value with the same name in the same scope
+// So we export the component with a different name, and users can import the type separately
+import { OnboardingSlide as OnboardingSlideComponent } from "./presentation/components/OnboardingSlide";
+export { OnboardingSlideComponent };
+export type { OnboardingSlideProps } from "./presentation/components/OnboardingSlide";
+
+// For backward compatibility, export component as OnboardingSlide
+// Users should import type as: import type { OnboardingSlide } from '@umituz/react-native-onboarding'
+// And component as: import { OnboardingSlideComponent } from '@umituz/react-native-onboarding'
+// Or use the alias: import { OnboardingSlideComponent as OnboardingSlide } from '@umituz/react-native-onboarding'
+export { OnboardingSlideComponent as OnboardingSlide };