Introduce @floating-ui/vue package

[lozinsky]

This sources from the vue-floating-ui package. So far, it provides positioning only.

Next, I'd like to research the possibility of adding interactions to this package. But I'm not sure that I can keep compatibility with Vue 2. Because development of components with vue-demi is too hard vueuse/vue-demi#153.

• vue installs with their own types for JSX that conflict with react (unfortunately I had to use patch-package to remove Vue JSX types Make JSX typings an optional install as they conflict with React TSX vuejs/core#1033)

[rollingversions]

@floating-ui/vue (unreleased → 0.1.0)

New Features

• Initial release

Packages With No Changes

The following packages have no user facing changes, so won't be released:

• @floating-ui/core
• @floating-ui/dom
• @floating-ui/react
• @floating-ui/react-dom
• @floating-ui/react-native

Edit changelogs

[netlify]

✅ Deploy Preview for vibrant-gates-22c214 canceled.

Name	Link
🔨 Latest commit	a2d4f47
🔍 Latest deploy log	https://app.netlify.com/sites/vibrant-gates-22c214/deploys/6399d2d78d4ae30009f1275c

[atomiks]

Is this ready for review now? Thanks for this, it looks great 😄

Regarding the docs: for now, it should be commented out of the navigation. Once it's released on npm, I'll uncomment it (there will be a delay, so it won't exist).

[lozinsky]

Is this ready for review now?

Yep 🙂

Regarding the docs: for now, it should be commented out of the navigation.

I've added hide: true.

[atomiks]

It looks great to me, but my Vue knowledge is very limited. Anyways, if there are any issues, people can file them 😄 In the meantime, we can start it as v0 major until a few months have passed with it being vetted by lots of usage, then bump it to v1

[renatodeleao]

@lozinsky just want to thank you for doing this! Had to spin up my own package as well (floating-ui-x), because popular Vue community packages didn't follow the low-level approach of the original. It is so much better to take advantage of the popularity of this repository: more people, and more contributors = better code!

Developing Vue2/3 hybrid is indeed very painful when components are involved. Composables are "managable" from vue@>2.7.x but not sure if we should add that maintenance burden at this point (vue2 EOL next year). Been contributing to a few packages with that approach and my advice is that is just not worth it. It's a rabbit hole, especially when it comes to testing.

I will try to help with a few PRs for the interactions package, made very basic attempts here but never got to the publishing part. Feel free to peak and bring something here if valuable.

Cheers! ✌️