datetimepicker
datetimepicker copied to clipboard
React 19
Feature request
Doesnt support react 19?
Why it is needed
This is needed so that we can use it with latest features in react
This is pretty much blocking me @as169m
this blocks me to upgrade expo
điều này ngăn cản tôi nâng cấp expo
+1 I can't upgrade expo either
Same here. Getting the following error on updating from expo 52 to 53:
'Log files:
/Users/brandtnewlabs/.npm/_logs/2025-05-05T17_32_47_007Z-debug-0.log
# npm resolution error report
While resolving: [email protected]
Found: @react-native-community/[email protected]
node_modules/@react-native-community/datetimepicker
@react-native-community/datetimepicker@"8.3.0" from the root project
Could not resolve dependency:
@react-native-community/datetimepicker@"8.3.0" from the root project
Conflicting peer dependency: [email protected]
node_modules/react
peer react@"^19.0.0" from [email protected]
node_modules/react-native
react-native@"0.79.2" from the root project
peer react-native@"*" from @react-native-community/[email protected]
node_modules/@react-native-community/datetimepicker
@react-native-community/datetimepicker@"8.3.0" from the root project
peer react-native@"*" from [email protected]
node_modules/expo
expo@"^53.0.0" from the root project
peerOptional expo@">=50.0.0" from @react-native-community/[email protected]
node_modules/@react-native-community/datetimepicker
@react-native-community/datetimepicker@"8.3.0" from the root project
peer expo@"*" from @expo/[email protected]
node_modules/@expo/dom-webview
peerOptional @expo/dom-webview@"*" from [email protected]
peer react-native@"*" from @expo/[email protected]
node_modules/@expo/dom-webview
peerOptional @expo/dom-webview@"*" from [email protected]
peer react-native@"*" from @expo/[email protected]
node_modules/@expo/metro-runtime
peerOptional @expo/metro-runtime@"*" from [email protected]
node_modules/expo
expo@"^53.0.0" from the root project
peerOptional expo@">=50.0.0" from @react-native-community/[email protected]
node_modules/@react-native-community/datetimepicker
@react-native-community/datetimepicker@"8.3.0" from the root project
peer expo@"*" from @expo/[email protected]
node_modules/@expo/dom-webview
peerOptional @expo/dom-webview@"*" from [email protected]
peer react-native@"*" from [email protected]
node_modules/react-native-webview
react-native-webview@"13.13.5" from the root project
peerOptional react-native-webview@"*" from [email protected]
node_modules/expo
expo@"^53.0.0" from the root project
peerOptional expo@">=50.0.0" from @react-native-community/[email protected]
node_modules/@react-native-community/datetimepicker
@react-native-community/datetimepicker@"8.3.0" from the root project
peer expo@"*" from @expo/[email protected]
node_modules/@expo/dom-webview
peerOptional @expo/dom-webview@"*" from [email protected]
Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
As a temporary workaround, you can use the new DateTimePicker from expo-ui
As a temporary workaround, you can use the new DateTimePicker from expo-ui
Will this just work for iOS and not android?
@Drivez
Yes, it also works on Android. However, keep in mind that this library is still in alpha. It works well, but some features like setting a minimum or maximum date are not yet available: expo-ui-android
I just discovered another solution, though I’m not sure if it only applies to my case or if it works for everyone. I switched from pnpm back to npm, ran the project again, and the datetimepicker started working properly.
any updates regarding this?
Has no one been able to fix this yet?
A quick hack that worked for me is to do npm install --legacy-peer-deps.
At least I got my Expo Go running again for now.
Same issue
any alternative? seems like a dead project. Getting into React was the worst decision indeed.
👋 I'm constantly working on an alternative https://github.com/s77rt/react-native-date-picker/
Let me just say, this library is compatible with react 19. It's just npm that gives this annoying error without providing any helpful instructions.
You can create a .npmrc file and put legacy-peer-deps=true in there to avoid this error.
A PR that actually fixes the issue is welcome; this issue has attracted enough attention for someone to contribute.
Thank you!