Implementation of @floating-ui primitives for platforms other than React.
- keep api as close as possible to the original package, so that we can leverage their existent documentation site. Exceptions can be made if platform has a fundamental different way of doing things.
- make it good enough to request integration into
floating-uimonorepo, because I don't deserve nor want the burden of maintaining this alone.
I'm adding this chapter in the unlikely event of this getting shared somewhere. Why aren't you writing this in TypeScript in 2022?! Are you mad mate?!:
No, I just prioritize features over types for the free time I will spend on this. I've worked with TypeScript but I'm not a TypeScript jedi neither a fanboy. As such, I prefer to spend my free effort on keeping feature-parity with the original package than in finding solutions for the type hieroglyphs problems that come from consumers of "platform X" package. The cost does not yet justifies the means, because typescript is very time consuming for library developers1, can be a barrier for contributors and this is just a personal project for now.
If you reading this and want TypeScript so badly, please note that I accept the corresponding type definitions files, and even kickstart this with some a few ones — See i'm not that stubborn. Happy to take any improvements on those. Here's some guidelines on how to do it take some of the points with a pinch of salt. But as i've said before, if someone contributes with a cool feature that works but can't make tsc happy I will ship it anyways.
Because poppers/tooltips/fly-outs are something I'll use in every web project during my dev career, independently of the tech stack, and popper.js (now floating-ui) is the best position engine out there.
It started as a fork from allindevelopers/vue-floating-ui#1