Replies: 4 comments 8 replies
-
Probably radix also needs to be updated to remove those warnings about forwardRef: radix-ui/primitives#2811 there is a PR already with a fix for slots etc |
Beta Was this translation helpful? Give feedback.
-
I'm keeping an eye on radix-ui/primitives#2811 (I've been testing the patch and so far so good). |
Beta Was this translation helpful? Give feedback.
-
https://github.com/shadcn-ui/ui/blob/main/apps/www/registry/new-york/ui/button.tsx |
Beta Was this translation helpful? Give feedback.
-
I am still facing the issues till this date. Any update on this issue? |
Beta Was this translation helpful? Give feedback.
-
Hi, @shadcn!
What's the plan for React 19?
Next.js was updated to React 19 on their Canary release. v14.3.0-canary.46.
Resulting in some warning messages and errors:
"Warning: Accessing element.ref was removed in React 19. ref is now a regular prop. It will be removed from the JSX Element type in a future release." and "TypeError: Cannot read properties of undefined (reading 'ReactCurrentDispatcher')".
Some of the changes in React 19:
I'll wait to update Next.js for now, but I just wanted to hear when we can expect a huge change to a lot of your amazing components that use React.forwardRef today. 🙏
Beta Was this translation helpful? Give feedback.
All reactions