The first stable release. Moves bottom-sheet presentations to the TrueSheet-based BottomSheet in heroui-native 1.1.1, adds validation details to DateField, targets Expo SDK 58 and React Native 0.88, and fixes a screen memory leak.
HeroUI Native Pro 1.0.0 is the first stable release. It adds no new components. Every bottom-sheet presentation now runs on the native TrueSheet-based BottomSheet from heroui-native 1.1.1, DateField reports what the user typed so you can validate it, and the library is built and tested against Expo SDK 58 and React Native 0.88. Bottom-sheet props are a breaking change: read the Breaking Changes below before you upgrade.
Follow the installation guide to authenticate the private registry with your HEROUI_PERSONAL_TOKEN, install heroui-native-pro, and wire up HeroUINativeProvider.
Update to the latest version, together with heroui-native (^1.1.1 is now required):
npm install heroui-native-pro@latest heroui-native@latestpnpm add heroui-native-pro@latest heroui-native@latestyarn add heroui-native-pro@latest heroui-native@latestbun add heroui-native-pro@latest heroui-native@latestIf you use a bottom-sheet presentation anywhere, also install the new optional peer @lodev09/react-native-true-sheet (^4.1.0). It replaces @gorhom/bottom-sheet, which you can remove if nothing else in your app uses it. Rebuild the app after installing it, since the package ships native code:
npm install @lodev09/react-native-true-sheetpnpm add @lodev09/react-native-true-sheetyarn add @lodev09/react-native-true-sheetbun add @lodev09/react-native-true-sheetnpx expo install @lodev09/react-native-true-sheetheroui-native 1.1.1 rebuilds BottomSheet on TrueSheet, a native sheet, and every Pro component with a bottom-sheet presentation follows it: Autocomplete, DateField, DatePicker, DateRangePicker, DateTimePicker, and TimePicker. Their Content part now forwards BottomSheet props (detents, draggable, grabber, background, backgroundBlur, and so on) instead of @gorhom/bottom-sheet props.
detents={[0.9]}, so it keeps its height while the keyboard opens and the list filters. The sheet moves with the keyboard natively, so the keyboard props and sheet-aware focus handlers are gone. (Documentation)draggable={false} and grabber={false}, so scrolling the wheel never drags the sheet. It closes through the dimmed area or the trigger. (TimePicker, DateTimePicker)background or backgroundBlur to BottomSheet to customize it.<Autocomplete presentation="bottom-sheet">
<Autocomplete.Trigger>
<Autocomplete.Value />
<Autocomplete.TriggerIndicator />
</Autocomplete.Trigger>
<Autocomplete.Portal>
<Autocomplete.Overlay />
{/* detents replaces snapPoints; 0.9 is the default */}
<Autocomplete.Content presentation="bottom-sheet" detents={[0.6]}>
<Autocomplete.SearchField />
<Autocomplete.List />
</Autocomplete.Content>
</Autocomplete.Portal>
</Autocomplete>DateField onValueChange now receives a second details argument with inputText, isComplete, and isValid. In "masked" mode it fires on every edit, so you can tell an empty field from a partial date or an impossible one such as 31/02/2003. Handlers that take one argument keep working.
import type { DateFieldValueChangeDetails } from "heroui-native-pro";
function getDateError(details: DateFieldValueChangeDetails) {
if (details.inputText === "") return undefined;
if (!details.isComplete) return "Finish typing the date";
return details.isValid ? undefined : "Enter a real date";
}
<DateField
isInvalid={error !== undefined}
onValueChange={(next, details) => {
onDateChange(next);
setError(getDateError(details));
}}
>
<Label>Event date</Label>
<DateField.InputGroup>
<DateField.Input />
</DateField.InputGroup>
<FieldError>{error}</FieldError>
</DateField>;The masked input also keeps its value in sync with the text: a complete valid date is committed as you type, and onValueChange receives undefined as soon as the text stops being a valid date. Typing re-renders only DateField.Input, so the docs now recommend uncontrolled usage (defaultValue + onValueChange). See the DateField component page.
The library and example app are built and tested on Expo SDK 58 and React Native 0.88.1, with React 19.3, Reanimated 4.7.1, Worklets 0.13, Gesture Handler 3.3, Screens 4.30, and Pager View 9. Types are updated for the strict React Native 0.88 type definitions.
scheduleOnRN no longer keep an unmounted screen in memory. This affected SwipeableRow, SlideButton, ProgressButton, FAB, WheelPicker, Carousel, Agenda, LiveChart, SplitView, and the charts (#131).31/02/2003 are rejected instead of being clamped to the last day of the month (#121).01/01/0100), so blur no longer clears a valid date (#121).minValue / maxValue, instead of running until the finger lifts (#117).--radius instead of a hardcoded pill, so themes with a smaller radius render correctly. The default theme still renders a full pill (#120).heroui-native peer dependency to ^1.1.1.@lodev09/react-native-true-sheet (^4.1.0) as an optional peer for bottom-sheet presentations.BottomSheet propsContent with presentation="bottom-sheet" on Autocomplete, DateField, DatePicker, DateRangePicker, DateTimePicker, and TimePicker no longer accepts @gorhom/bottom-sheet props such as snapPoints, enableDynamicSizing, enablePanDownToClose, handleComponent, backgroundComponent, or the keyboard props. Pass BottomSheet props from heroui-native 1.1.1 instead (all of them except name and TrueSheet's own presentation).
Before:
<Autocomplete.Content
presentation="bottom-sheet"
snapPoints={["60%"]}
enableDynamicSizing={false}
keyboardBehavior="extend"
>
...
</Autocomplete.Content>After:
<Autocomplete.Content presentation="bottom-sheet" detents={[0.6]}>
...
</Autocomplete.Content>To make a TimePicker or DateTimePicker sheet draggable again, pass draggable and grabber yourself:
<TimePicker.Content presentation="bottom-sheet" draggable grabber>
...
</TimePicker.Content>In "masked" mode, DateField used to commit the parsed date on blur and keep the last valid value while the text was edited. It now calls onValueChange(undefined, details) as soon as the text stops being a complete valid date, and calls onValueChange on every edit. If your handler does work on each call (a network request, for example), check details.isValid first or compare value with the previous one.
heroui-native must be ^1.1.1 (was ^1.0.11).@gorhom/bottom-sheet is no longer used. Install @lodev09/react-native-true-sheet (^4.1.0) if you use a bottom-sheet presentation.