Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - [DateRangePicker] - Invalid prop ref supplied to React.Fragment. React.Fragment can only have key and children props. #4358

Closed
J4v4Scr1pt opened this issue Dec 13, 2024 · 5 comments · Fixed by #4428
Assignees
Labels
📦 Scope : Components Related to the components 🐛 Type: Bug Something isn't working

Comments

@J4v4Scr1pt
Copy link

NextUI Version

2.6.8

Describe the bug

I'm upgrading my project to NextJs 15 and React 19, all works well so far but found an issue when using the DateRangePicker.

Your Example Website or App

https://codesandbox.io/p/devbox/nk4vk2?file=%2Fapp%2Fpage.tsx%3A2%2C10-2%2C25

Steps to Reproduce the Bug or Issue

Open the CodeSandbox and open the DateRangePicker. There will be an error showing up.

Expected behavior

To not have the error :)

Screenshots or Videos

image

Operating System Version

Window 11

Browser

Chrome

@shlyamster
Copy link
Contributor

I have the same error

@wingkwong
Copy link
Member

Currently it is only compatible with react 19 rc, since react-aria still hasn't supported react 19 yet.

@J4v4Scr1pt
Copy link
Author

Currently it is only compatible with react 19 rc, since react-aria still hasn't supported react 19 yet.

Ok, understand. Then we can keep track of it until they support LTS React. :)

@wingkwong wingkwong self-assigned this Dec 22, 2024
@wingkwong
Copy link
Member

seems not related to react 19. this sandbox https://codesandbox.io/p/devbox/friendly-diffie-55mxp5 can reproduce the error with react 18.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 Scope : Components Related to the components 🐛 Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants