You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to directly use this library, without the requirement of popperJS. One possible solution would be to make popperJS an optional peer dependency, and allow for custom handling of the "popperInstance" in the implementation. It will allow for more granular control in the implementation while still allowing for default behavior to be implemented using popperJS.
I have looked at floating ui and I do want to move to it at some point. Well bootstrap is no longer a dependency, I'm guessing that's where most people are using it. BS5 moved to popper 2 and they have opened tickets to migrate as well. If I simply migrate now, most people will have yet another dependency.
I would consider a PR that hide the implementation that defaulted to popper but could be overwritten in a plugin to use floating ui or w/e. That's probably the way forward anyway.
Prerequisites
Proposal
Remove the requirement for popperJS and add support for using FloatingUI.
I have a partial implementation here.
Motivation and context
I'd like to be able to directly use this library, without the requirement of popperJS. One possible solution would be to make popperJS an optional peer dependency, and allow for custom handling of the "popperInstance" in the implementation. It will allow for more granular control in the implementation while still allowing for default behavior to be implemented using popperJS.
For more info on migrations see https://floating-ui.com/docs/migration
The text was updated successfully, but these errors were encountered: