-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use it with vitest #7163
Comments
This project isn't being maintained so I'd suggest you look at migrating away from the library. |
@Hiws What does this mean? I didn't find information about BootstrapVue not being maintained. |
There's no one to maintain it. |
@Hiws I think there should be a call for maintainers at the very top of the readme and the website 🙂. |
Vue 2 is going EOL in a few months. So don't see any worth in continuing maintaining this project. For people who want to upgrade to Vue 3, then https://github.com/bootstrap-vue-next/bootstrap-vue-next should be the best option. |
@Hiws Oh I didn't know of this guy! Thanks for that! |
Recommending upgrading to an alpha library is not a good suggestion. This library still has value up to the point next is stable. Also, it works on Vue 3 (to some extent) with compat. |
Hey, I'm trying to use BootstrapVue with Vitest and I get errors when instantiating a Vue instance because it will always resolve
vue@^3
instead of@vue/compat
and then throws errors related toVue.extend
inportal-vue
. Tried all environments (Node, jsdom, happy-dom, Edge). Although it is a Vitest issue, I thought I ask here about ideas because BootstrapVue is the main reason why I'm using@vue/compat
and haven't migrated tovue@^3
yet.Maybe it's also worth documenting how to use it with Vitest.
Wasn't sure what category to use for this issue, feel free to move it somewhere else.
The text was updated successfully, but these errors were encountered: