Bootstrap v5 support #5507
Comments
|
Maybe it would be worth pinning this issue so that it is more visible to people? |
|
|
@Hiws Can this be pinned please? |
|
Yes please pin, I had to go look for it glad I found it. |
|
Please, keep in mind that several developers which run enterprise application won't switch to Vue 3 due to lack of plugins not ready for vue 3 itself, but they wish to benefit of bootstrap 5 improvements. |
We are looking into supporting both Vue 2 and Vue 3 with the BootstrapVue 3 release by utilizing https://github.com/antfu/vue-demi which looks pretty promising. |
Please don't rewrite the project. Thousands of hours have gone into this project along with thousands of bugfixes, improvements, etc... Experience that all will be undone by rewriting the project, it will take years to get to the same level of features, refinement and bugless-ness with the end result that you're basically at the same point as you were a couple of years before, only now it's been "re-written". |
Not sure why you are getting down voted. Bootstrap-vue should upgrade to Vue3 by continuing to use the Options API, and then slowly change it over to the composition API. |
|
Is there ETA now for BS5 + Vue3? Sorry for this but I wasn't able to find a new update on this. |
|
@jd-0001 Bootstrap just moved v5 stable release target to February 2021. I'd be likewise interested to know how long it might take to have BSV on BS v5 after v5 has reached stable version? To have some estimate of this years framework update schedule targets. |
|
@jackmu95 now that Vue 3 support upgrade has taken a longer route, does it reduce the amount of work to be done for achieving BS 5 support, as earlier it was mentioned that BS 5 based version will be a complete rewrite? |
|
Bootstrap 5 support is a major breaking change and requires completely different changes than the ones for Vue 3 support. We first need to finish the changes for Vue 3 which will ship in BootstrapVue v3. I can't promise right now when BV v4 will ship after the Bootstrap 5 release, but it is less work supporting Bootstrap 5 than Vue 3. We should be able to have a BV release 1 or 2 months later. BootstrapVue v3 (with Bootstrap v4) support will also match the EOL from Bootstrap. |
|
What about Vue 2 + Bootstrap 5? It seems Vue 2 will stay for quite a while. |
I believe the current plan is still for BootstrapVue 3 to support both Vue 2, and Vue 3. |
|
Why not rename BootstrapVue v4 to BootstrapVue v5, so it has the same number as Bootstrap 5?I think it will be less confusing for new users. |
|
Now that Bootstrap 5 has dropped jquery, is there any advantage to using BootstrapVue with BS v5? For example: https://dev.to/codeply/using-bootstrap-5-with-vue-js-5fnp What would the advantage be of using a wrapper like BootstrapVue vs a direct integration like the above example? |
|
@binaryfire I have actually been building my own Bootstrap v5 library because we're in a situation where we can't wait for BootstrapVue. There have only been a few tricky bits with getting it to work with Vue, overall it's been a lot easier than I expected though. Saying that, I wouldn't recommend it if you're in a situation where you can wait. You're still having to do all of the boilerplate work that library will handle for you. Creating a component, creating all the various prop/slot options you need, and getting the Bootstrap javascript to work. It's still time consuming. Some components are very simple, whereas some need a lot of time. If you need it now and only need a small amount of components, you should go that route. But if you can wait, you should because you're still avoiding all the integration and boilerplate work. |
|
@MechJosh0 Thanks, that's very helpful. Looks like I'll be waiting :) We're starting work on a new app soon so I want to use Bootstrap 5 and Vue 3 from the start. Hope a new version isn't too far! |
|
Bootstrapvue contains several components that are not available with Bootstrap5 such as form tags, overlay, skeleton, etc. that’s why I use BootstrapVue. |
|
When we can expect Vuejs 3 support coming? |
Wrong issue. |
|
I'm waiting for bootstrap 5 and vue 3 support since long ago. there is no option for me but to go for pure bootstrap. |
|
The final beta of Bootstrap 5 was released last week: https://blog.getbootstrap.com/2021/03/23/bootstrap-5-beta-3/. The RC won't be far off now. I love BootstrapVue but the reality is no-one starting a new Bootstrap project today is going to build it with Bootstrap 4. Or Vuejs 2. I understand the need to maintain the current codebase for existing projects, but BootstrapVue won't be able to compete with other frameworks if it leaves it much longer. For example Vuetify have already released an alpha of their Vuejs 3 rewrite: https://vuetifyjs.com/en/introduction/roadmap/ I hope we see some progress on a new version soon. If there's a link where I can donate towards a BS5 / Vue3 rewrite please let me know. I'd be happy to contribute! |
|
The major version number should be synced to Bootstrap version imo. I find it quite confusing knowing which is for which when combined with Vue version numbers and changes. So BootstrapVue version that supports Bootstrap 5.x should also be v5.x and scrap the idea of calling it v4 altogether. |
Why sync with Bootstrap version? Why not Vue version? Or why not based on how versions should be done. The package version should not be dictated by the dependency versions it uses. Major versions should be by breaking changes as per the majority understanding of how versions are used.
|
|
or,use primevue,free and vue3 ready |
|
Hi guys It would be great to get a comment from one of the maintainers on this issue. Bootstrap 5 is out now and being used. Are there actually plans to move to v5 or will this remain a legacy / v4 framework? And if there will be a move to v5, do you have a roadmap or timeframe? Even some approximate timeframes for when the team will start actively working on a v5 branch and when the target is for an alpha release would help. Months? Next year? That way we can at least make a decision on whether we can wait or move to a different framework. The radio silence isn't great. |
|
Honestly, a public roadmap will be really appreciated. |
|
Your mileage will certainly vary, but if you're lucky and have a relatively small app depending on a limited number of components (like I do), you might find that refactoring to a simple Vue / Bootstrap 5 stack (bypassing BootstrapVue altogether) is much easier than expected (upgrading to Vue3 as a bonus while you're at it), and much less work than refactoring to a completely different framework. If this issue is solved at some point in the future, you can then consider progressively plugging this framework back into your stack (if there is then any point in doing that) with less refactoring than if you had gone a completely separate route. Or maybe you'll then find that V3/B5 spiced up with custom JS is honestly good enough to keep you going. Whichever way you choose to go as you move on, good luck! |
I've been using BS5 with Vue2 and NuxtJS for the past few months. I am eagerly awaiting for BSVue, but I am not sure if I really will need it. If you watch the Bootstrap5 Github project/issue list, you'll see that some of the BSVue components are actually being created for Bootstrap5, such as Skeleton and I think there's an Overlay component coming, as well. Form validation state is now easy with Bootstrap5 too. Two things that I find highly valuable from BSVue are 1.) Tree shaking/documentation 2.) Form Tag component....ok and 3.) excellent support from @Hiws over at the BSVue Discord channel (thankfully not Slack). For maintainability, I think it may be better to minimize the number of frameworks in your app...and just using Bootstrap5 and Vue may be all that is needed, especially now that JQuery has been dropped from Bootstrap (it's easy to use vanilla JS with it). Maybe rather than trying to recreate all the current Bootstrap components, BootstrapVue can just give us more components that are not available with BS5 (avatar components, better navbars, dynamic tables, etc). Something like TailwindUI.com. Just a thought! Love BSVue and I know I will still use it where/when needed. I've made my donation to the project. |
|
I think that's the way to go: forget about being a "platform" - Bootstrap stands on it's own without shims now and doesn't need a platform, especially one which has to keep up with it. Instead, Bootstrap Vue has a set of components, some of which are best-in-class. So either split the project so the components are stand alone, or curate them as a set of components, not a "platform". It's a mindset change, but it's much easier to keep the table component up to date than an entire "framework", much of which most people don't want or need. |
|
If you need Bootstrap 5 and Vue 3 support you can try the latest version of CoreUI for Vue.js - https://github.com/coreui/coreui-vue/tree/v4 |
|
In web https://bootstrap-vue.org/ Not yet support vue3 and bootstrap 5 ? |
|
Just saw this. OUCH. |
|
Is there any activity around this? I'm starting a new project, and it would be really nice if I could use Bootstrap 5 with Vue 2. |
I think this project is basically a dead end now. I certainly wouldn't recommend it for new projects. |
|
So is this happening? Need it for our shared style sheets. Our websites are already updating to BS5. |
|
you probably can check out: https://github.com/cdmoro/bootstrap-vue-3 or |
|
For anyone out of the loop (since this thread hasn't received the updates that the other one has):
For details on progress, follow updates in the other thread covering the overall status of the project: Project status & roadmap. The most recent major update in that thread is the release of v2.22.0, with notes about the promising progress of the v3 rewrite. You can read the full update here. |
|
What is the currently recommended course to update a project using bootstrap-vue, Bootstrap 4 (EOL) and Vue2 (EOL) in such a way that no EOL versions are used any more? Even bootstrap-vue-next considers itself "alpha". |
and others
Recently Bootstrap announced the first v5 Alpha: https://blog.getbootstrap.com/2020/06/16/bootstrap-5-alpha/
Just raising this issue to gather ideas how a potential migration plan might look like.
The text was updated successfully, but these errors were encountered: