Patch Changes
-
#1868
e8e14beThanks @github-actions! - Declare the./devsupportsubpath inexportsand stop the package importing itself.Four internal modules imported through the package's own name —
progressBarand
circularProgressBarpulled from@ui-kitten/componentsitself, a circular import of the
package barrel, whilemodalandcalendarHeaderreached in via undeclared subpaths.
Metro reported these asnot listed in the "exports"and fell back to file-based
resolution; they now use relative imports../devsupportis a real public surface (RenderProp,TouchableWebElement) and is now a
declared export with its own types, react-native, source, and default conditions.
Bundling a consumer app produces noexportswarnings. -
73e517fThanks @bataevvlad! - ExportAutocompleteRef,InputRef, andListReffrom the package root.All three were defined and exported by their own modules but never re-exported from the
barrel, so consumers had no way to type a ref forAutocomplete,Input, orList—
the same gap that madeIconRefunusable in practice. They now sit alongside the
already-exportedCalendarRef,DatepickerRef,RangeCalendarRef,RangeDatepickerRef,
andSelectRef. -
#1868
92eedc8Thanks @github-actions! - Ship generated type definitions instead of raw source.typespointed at./index.ts, so consuming projects typechecked the library's own
source under their tsconfig and saw 221 errors fromnode_modules— with no workaround,
sinceskipLibCheckonly skips.d.tsfiles. The package now builds.d.tsvia
react-native-builder-bob'stypescripttarget and pointstypesat
./lib/typescript/index.d.ts.Fixing the 22 type errors that blocked declaration output also corrected real bugs:
React.ReactTextwas removed in React 19; replaced withstring | numberacross 19 sitesCalendar'sgetViewMode()was typed() => stringbut returns aCalendarViewModeTabView's view pager ref was typed as the component value rather thanViewPagerRefDatepickerPropsdeclared conflictingonBlur/onFocusinherited fromViewPropsdateServicewidened toNativeDateService | DateService<D>instead ofDateService<D>
Button,Select, andDatepickernow acceptstring | numberfor text props, matching
CheckBox/Toggle/Radioand the runtime behaviour ofFalsyText. Previously the
idiomatic<Button>TEXT</Button>did not typecheck.Type-only changes — the compiled bundle is byte-identical.