Migration to FloatingUI #3842
Comments
|
Agree that it would be awesome if In our design system we're already using floating-ui for a lot of other tasks and it would be awesome if we wouldn't load multiple positioning libraries at the same time. I can start working on a PR for this given there's interest from the maintainers. |
|
Feel free to make a PR to migrate. |
G07cha
added a commit
to G07cha/react-datepicker
that referenced
this issue
Nov 26, 2023
G07cha
added a commit
to G07cha/react-datepicker
that referenced
this issue
Nov 26, 2023
Breaking changes: - `popperModifiers` only accepts [Floating-UI specific middleware](https://floating-ui.com/docs/middleware) - 'auto', 'auto-start', and 'auto-end' placements are no longer supported - `popperProps` only accept [`useFloating` options](https://floating-ui.com/docs/usefloating#options) Closes Hacker0x01#3842
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to this discussion,
popperjs/corehas been rebranded as FlotingUI. The previous version will be kept in a low maintenance mode, as the new library@floating-ui/poppertakes its place.Are there any plans to migrate internal mechanisms so that they utilize this new library?
The text was updated successfully, but these errors were encountered: