Project status & roadmap

[xanf]

TL;DR (last update: Oct 25, 2022)

✅ v.2.23.0 with initial support of Vue.js 3 released 🎉

Next steps:

• Publish initial rewrite infrastructure (includes CI, automated comparison of render output with v2.23.0)
• Rewrite each components one by one and reach feature parity with v2.23.0
• Explore Bootstrap v5 compatibility

Longer version

Bootstrap-Vue is heading towards Vue.js 3. Our main goals remain the same:

• we do not want to introduce as few breaking changes as possible (ideally 0). We respect our existing users and understand that Vue2 -> Vue3 migration is already quite painful so we do not want to add extra one
• we want to migrate to TypeScript, Vite and SFC for Vue.js 3 to simplify contributions to this project
• migration to Bootstrap v5 is definitely on the priority list but right after previous step

I will keep you posted on updates

Original description from December 2021

# TL; DR

• New maintainers are here
• Pull requests will be reviewed within several days
• There will be a new release of bootstrap-vue coming with fixes included
• Primary goal of the team is to rewrite bootstrap-vue to support Vue 3 and Bootstrap v5. We will do this in a separate repository. We will announce the detailed roadmap for a rewrite as soon as we have it

Long version

Hello there! It's been a tough year for all of us, and bootstrap-vue is not an exception.

The real power of opensource is that it is always about community. And the very first words of my gratitude will be to every person who contributed here - by opening an issue, making a pull request, posting a comment, or just starring the repository. My second gratitude comes to @Hiws, who helped people so long in this repository.

bootstrap-vue is not dead, and after a long period of silence, it has new people in the org added - it's me and @cdmoro (invitation is pending, but I personally hope he will join us!). While our primary interest is making bootstrap-vue modern & fancy - to add support Vue 3 and Bootstrap v5, it does not mean this repo is abandoned.

Starting from tomorrow, I will go through the pull requests and review them. Afterward @pi0 is going to do a release of bootstrap-vue package with all the changes.
I will also try to do my best in cleaning issues (but obviously with lower priority)

Now about the rewrite. We've set up a separate repository for that. It will be private just for a few days to set up the initial structure, flesh out project goals/non-goals, and our coding style. After that, it will be open to everyone - everyone can contribute! 🎉

Right now I have my own vision of the goals for rewrite, but since now I'm speaking "officially" I would like to postpone announcing them. Stay tuned and thank you again!

---

Updated roadmap

💀 "end-of-life" goal for current bootstrap-vue code

There definitely will be two more minor releases:

• one with all available and acceptable pull requests merged. I'm working on this personally and I hope this will be ready before Jan 7th
• one with @vue/compat compatibility, but only for { MODE: 2 }. This will allow people start migrating their code to Vue3 while rewrite project is in progress.

There might be additional releases if we will discover any important regressions in current code

Rewrite

⭐ Goals:

• provide release for Vue3 using bootstrap v4 compatible with current bootstrap-vue API (including props, events, slots, etc.) as much as possible.
• provide clear migration path for features, impossible to migrate (for example $root)
• provide compatibility build for rewrite for Vue2. Compatibility build will be using @vue/composition-api and will allow us to deprecate current codebase entirely and promote new code as single source of truth
• migrate to bootstrap v5 as soon as rewrite to Vue3 will be complete (all existing components ported)
• always keep a11y in mind, providing sane defaults but also including as much ARIA extension endpoints as possible. This one, I believe needs detailed explanation. Providing good a11y is always trade-offs making "good a11y almost impossible for generic components library like a11y. Providing "extension" points is pretty straightforward - each component, which potentially might need aria attributes will have it's dedicated computed for that (for example toggleButtonAria, hideButtonAria etc. We will promote this as an official way of "tuning" bootstrap-vue components extending them (well, for setup it just means calling setup and consuming return values and redefining such computeds. These computeds will be added where we think it is appropriate but generally any user could easily request "a11y" extension point for any component if he/she needs that. I feel this like a good balance between making good components possible and diving forever in a11y/ARIA discussions

🔧 Implementation details

For new repository we will be using:

• single-file components to leverage powerful optimzation engine behind Vue compiler and to make it easier to contribute
• TypeScript
• Composition API and <script setup>.

📓 Basically flow of reimplementing component will be:

• copy component tests from old repository. We will possibly temporary allow use js for tests to focus on real code :). These tests by utilizing vue-test-utils-compat will be a reference for initial implementation
• implement component for vue 3. Verify it via tests and via examples extracted from documentation from old repository
• make it work with Vue 2
• make shiny docs work with Vue3 (hello Nuxt3)
• refactor tests to use vue-test-utils-next api. This will require reverse compatibility layer (running v2 tests on vue-test-utils v1) but this is quite easy
• Eventually merge new repository intro this one as separate "root" to keep one repository as single source of truth and not confusing people :)

[literakl]

Wow, crossed my fingers.

[alokVishu]

Wow, maza avse have. bapu.

[loeffel-io]

Fuck yeah 🕺

[vnguyen004]

Awesome! thanks for the update

[AlexanderWesten]

That is some great news! Looking forward to seeing the rewrite!

[bruce-ding]

Great news!

[smithy2954]

Great News.!!!!

[marcgdl]

Great news, I will be on the lookout for new news. !, Thanks.

[dimtrovich]

very great news. I look forward to this new version. I have chills

[carum98]

Good news, thanks

[muhammadshumas]

Finally.. Great news

[akhi-ninja]

Wow great news

[akhi-ninja]

What is the plan for releasing VUE3 component ? any ETA ?. Because the projects have larger codebase need more time to upgrade , If bootstrap vue doesn't have any ETA for Vue3 components release , the only option for them to move to another library

[todatasudata]

JFYI: https://github.com/coreui/bootstrap-vue (supporting vue-3) is just released

[akhi-ninja]

thanks @todatasudata I will look in to this , but looks like this is another library , is it a official bootstrap-vue vue3 component library ? , my point here is official contributors and maintainers is this library is widely used in so many enterprise application now Vue3 is stable and all of them planning to migrate application when is comes to enterprise app with large code base they plan for redesign app this include architectural changes as well , if bootstrap vue is not giving any plan for vue 3 support or dont have any ETA for vue3 supported component release they will not support this community and they move to another framework , similar component library Vuetify release beta version for vue3 and i think they are planning for Feb 2022 for first version (vue3 support ) . I love bootstrap and bootstrap vue i used this in multiple project . but if we are not updating components on time we loose users

[joshjhans]

Is coreui/bootstrap-vue the 'separate repository' for the rewrite? Has that been made public, yet?

[aceofwings]

The unofficial rewrite where people were contributing to was and still is CDMoro's Bootstrap Vue 3. Many of those components have 1 for 1 replacements. Core UI is a barebones UI framework that at the moment does not provide the level of utility found in components in Boostrap-Vue-3 and BootstrapVue. @akhi-ninja I suggest having more patience because these open source projects do not develop over night and your comments are certainly not helpful or encouraging to the contributors of these projects.

[akhi-ninja]

@aceofwings sorry if you feel wrong , i understand none of the opensource projects developed overnight , i posted this after waiting long time because there was no discussion or plan for vue3 components . I didn't mean to discourage any contributors , i really love this community and i don't want this community to be outdated . What ever I said is the fact we should act fast

[loeffel-io]

any news on this? @xanf

There will be a new release of bootstrap-vue coming with fixes included

[mrholek]

Is coreui/bootstrap-vue the 'separate repository' for the rewrite? Has that been made public, yet?

@joshjhans It's the Bootstrap 5 components library for Vue 3 maintained by CoreUI Core Team. Our goal is to create this library as simple as possible and add more features based on users' feedback. If you want you can check how it works here https://coreui.io/bootstrap-vue

[lianee]

FWIW: the coreui project might be interesting, but it is not an update and not even a fork of this project.
It is not compatible (just have a look at the table).
The only thing in common is the bootstrap CSS code, and I think the name is just misleading and causes the wrong confusion.

[xanf]

Hi, everyone and happy new year! Sorry for delay, we've spent some time figuring "common ground" between the project vision for all maintainers and I'm happy to provide you a roadmap update

💀 "end-of-life" goal for current bootstrap-vue code

There definitely will be two more minor releases:

• one with all available and acceptable pull requests merged. I'm working on this personally and I hope this will be ready before Jan 7th
• one with @vue/compat compatibility, but only for { MODE: 2 }. This will allow people start migrating their code to Vue3 while rewrite project is in progress.

There might be additional releases if we will discover any important regressions in current code

Rewrite

⭐ Goals:

• provide release for Vue3 using bootstrap v4 compatible with current bootstrap-vue API (including props, events, slots, etc.) as much as possible.
• provide clear migration path for features, impossible to migrate (for example $root)
• provide compatibility build for rewrite for Vue2. Compatibility build will be using @vue/composition-api and will allow us to deprecate current codebase entirely and promote new code as single source of truth
• migrate to bootstrap v5 as soon as rewrite to Vue3 will be complete (all existing components ported)
• always keep a11y in mind, providing sane defaults but also including as much ARIA extension endpoints as possible. This one, I believe needs detailed explanation. Providing good a11y is always trade-offs making "good a11y almost impossible for generic components library like a11y. Providing "extension" points is pretty straightforward - each component, which potentially might need aria attributes will have it's dedicated computed for that (for example toggleButtonAria, hideButtonAria etc. We will promote this as an official way of "tuning" bootstrap-vue components extending them (well, for setup it just means calling setup and consuming return values and redefining such computeds. These computeds will be added where we think it is appropriate but generally any user could easily request "a11y" extension point for any component if he/she needs that. I feel this like a good balance between making good components possible and diving forever in a11y/ARIA discussions

🔧 Implementation details

For new repository we will be using:

• single-file components to leverage powerful optimzation engine behind Vue compiler and to make it easier to contribute
• TypeScript
• Composition API and <script setup>.

📓 Basically flow of reimplementing component will be:

• copy component tests from old repository. We will possibly temporary allow use js for tests to focus on real code :). These tests by utilizing vue-test-utils-compat will be a reference for initial implementation
• implement component for vue 3. Verify it via tests and via examples extracted from documentation from old repository
• make it work with Vue 2
• make shiny docs work with Vue3 (hello Nuxt3)
• refactor tests to use vue-test-utils-next api. This will require reverse compatibility layer (running v2 tests on vue-test-utils v1) but this is quite easy
• Eventually merge new repository intro this one as separate "root" to keep one repository as single source of truth and not confusing people :)

[xanf]

Updated first comment in post :)

[xanf]

Another short note - I hope we will make repository of rewrite public in January. I'm against making it public on the early start of the project while we're setting up all boring infrastructure - it creates false expectation and mess. We will be happy to make it available to everyone as soon as we have first chunks of "really runnable" code

[Ericlm]

Does the incoming update and rewrite mean that the sass code will be updated to the latest sass syntax ? I remember having troubles with some bootstrap files when upgrading from node-sass to dart-sass (especially the division operator).

[Hiws]

Does the incoming update and rewrite mean that the sass code will be updated to the latest sass syntax ? I remember having troubles with some bootstrap files when upgrading from node-sass to dart-sass (especially the division operator).

I believe that's an issue with Bootstrap, and it has been fixed in 4.6.1.
So assuming BootstrapVue gets updated to support 4.6.1, then yes. The error should go away once that's done and people upgrade.
https://github.com/twbs/bootstrap/releases/tag/v4.6.1

[xanf]

@Scoottykun you've posted your message exactly on a day I had surgery (minor one, yet still recovering). I'm going to publish progress on September and going to dedicate at least 50 hours here. I think I'll start early next week. Please note, that is not by any means commitment to "release on September 30", but in spirit of visibility and iteration I would like to make progress public

[VividLemon]

@Scoottykun you've posted your message exactly on a day I had surgery (minor one, yet still recovering). I'm going to publish progress on September and going to dedicate at least 50 hours here. I think I'll start early next week. Please note, that is not by any means commitment to "release on September 30", but in spirit of visibility and iteration I would like to make progress public

What do you think the plan is for Bootstrap-vue-3 and mariusa's comment? I agree with mariusa that it is redundant to have two opposing Bootstrap adaptations to Vue. I only ask because you say you are planning on putting in some work, and would like to see work not wasted.

[DerAlbertCom]

This could be Bootstrap Vue for Vue 2 and 3 but Bootstrap 4 only. A switch to Bootstrap 5 requires even more work when updating the Application. And the @cdmoro Project can be Bootstrap 5 and Vue 3 only.

[timmi-on-rails]

The current version on vue3-compat-build branch fixes the issue (dropdown not working) of @graemedewe.

I do not have a lot of experience with npm/yarn. So if there is an easier way, please tell me.
Here is what I did:

1. Checkout branch

2. yarn install

3. yarn build

4. npm pack

5. Reference the resulting tgz file from my project package.json.

    ...
    "dependencies": {
      "bootstrap-vue": "file:../bootstrap-vue-XYZ.tgz",
    ...
   

Referencing the built git branch directory directly resulted in an error. (tgz works)

[ghenry]

Does this mean Bootstrap 5 is possible then too?

[xanf]

@ghenry this is mentioned on roadmap :)

[ghenry]

@ghenry this is mentioned on roadmap :)

It's only 3 on the list at the top of this issue! My apologies. How did I miss that...

Thanks.

[septatrix]

Does this mean Bootstrap 5 is possible then too?

If you do not require Vue 2 support you can also check out https://github.com/cdmoro/bootstrap-vue-3. I would say it is about 95% compatible and implement most features.

Also @xanf and @VividLemon are currently talking about if and how these projects might be merged in the future to not duplicate development effort though I assume it will be a complex topic and I am not expecting a resolution soon.

[Ericlm]

Thank you for the v2.23.0! It's a great step toward Vue 3, a big thank to everyone working on it to make this amazing framework looking toward the future 😊

[williamdes]

Does this mean Bootstrap 5 is possible then too?

If you do not require Vue 2 support you can also check out https://github.com/cdmoro/bootstrap-vue-3. I would say it is about 95% compatible and implement most features.

Also @xanf and @VividLemon are currently talking about if and how these projects might be merged in the future to not duplicate development effort though I assume it will be a complex topic and I am not expecting a resolution soon.

Newbie to Vue from today, bootstrap-vue-3 worked out of the box. It's maybe a great idea to merge the projects as I see on https://cdmoro.github.io/bootstrap-vue-3/reference/parityList.html that a lot seems to be already implemented.

[EagleTsui]

How to get $bvModal in setup

[ankurk91]

Take a look at 🚀
https://github.com/bootstrap-vue/bootstrap-vue-next

[Rukeeo1]

I believe it might be related to as this only appears in my console when I include the dropdown elements

vue.runtime.esm-bundler.js?fe26:5911 Uncaught (in promise) TypeError: 'set' on proxy: trap returned falsish for property 'id' at deepMergeData (vue.runtime.esm-bundler.js?fe26:5911:1) at deepMergeData (vue.runtime.esm-bundler.js?fe26:5911:1) at Proxy.mergedDataFn (vue.runtime.esm-bundler.js?fe26:6343:1) at applyOptions (vue.runtime.esm-bundler.js?fe26:6057:1) at finishComponentSetup (vue.runtime.esm-bundler.js?fe26:10636:1) at setupStatefulComponent (vue.runtime.esm-bundler.js?fe26:10521:1) at setupComponent (vue.runtime.esm-bundler.js?fe26:10425:1) at mountComponent (vue.runtime.esm-bundler.js?fe26:8715:1) at processComponent (vue.runtime.esm-bundler.js?fe26:8679:1) at patch (vue.runtime.esm-bundler.js?fe26:8247:1)

Hi, please what was your approach to solving this? I am trying to avoid re-writing that part of the code, because it's a legacy project.

[trandaison]

@ankurk91 This was bootstrap-vue-3, does it a official version for vue next?

[ankurk91]

You can ask repo owner youself

[mbabker]

Just so I'm clear and can plan some of my own organization's work correctly, is the https://github.com/bootstrap-vue/bootstrap-vue-next repository going to become the canonical next version of the Bootstrap Vue library (as in when 1.0 is tagged, we should be planning to move from this package/repository to that one)?

[VividLemon]

Just so I'm clear and can plan some of my own organization's work correctly, is the https://github.com/bootstrap-vue/bootstrap-vue-next repository going to become the canonical next version of the Bootstrap Vue library (as in when 1.0 is tagged, we should be planning to move from this package/repository to that one)?

Xanf was planning on putting out a statement, which never occurred. This is my "opinion":

Bootstrap-vue will likely not see continued support. There are no active maintainers to review prs, and nobody to fix the backlog of issues. I am capable of merging prs, but it's not very important to me to do so. The package is battle tested and can stand alone, without fixing some of the minor bugs that plague it. Vue 3 support that it achieved is nice, but some compatibility issues require some hacky workarounds, assuming you've found the relevant issues on the subject.

Meanwhile, the next repo will continue to see development by me, and occasionally others. This has the benefit of being fully Vue 3, TypeScript, and Bootstrap v5 compatible for those seeking to modernize.

Anyone can take what they want from this. There is no major reason that would necessitate a 1000 vue file change to upgrade from Vue 2 - Vue 3, and Bootstrap v4, to Bootstrap v5, and Bootstrap-vue to Bootstrap-vue-next. With Vue 2.7, many Vue 2 users have the increased benefit of better TypeScript, <script setup>, and other backported features. There may be some security questions for when Vue 2 reaches the end of life, however, Vue has never been known for excruciating security vulnerabilities.

There are, of course, benefits to upgrading, assuming it's not too much work. Of course, there are breaking migration changes. Bootstrap v5 comes with a nice set of new features, one of my favorites being "themes" in the 5.3 alpha. In addition, a nicer syntax for some things that Vue 2 would need to "hack together" for, eg, composables, etc.

The TLDR is that Bootstrap-vue will likely see no further changes. It is still usable, very stable, and can retire well. However, if you're willing to put in the work, Bootstrap-vue-next in a 1.0 release can be a nice upgrade to see, improved DX, Bootstrap v5, full Vue 3 support, and of course, an active maintainer. Upon 1.0, any new projects are encouraged to use it, unless you truly just love Bootstrap-vue.

[mbabker]

It's on the books for us to eventually do all the associated upgrades (BS4 -> BS5, Vue 2.7 -> Vue 3, and whatever the BootstrapVue upgrade path looks like). It's one of those things we've been OK with putting off while waiting for this package to catch up (with as much of our UI that's in Vue nowadays, it's just not practical for us to go back to Bootstrap's own JavaScript (be it BS4's jQuery or BS5's native code)) as everything's pretty darn stable and works nicely for us, so having a clearer picture of what that upgrade path will look like will definitely help us gauge the effort involved.

Thanks for the response.

[jeffsta9]

Question. As I'd Love to stick w/ Bootstrap-Vue, I'm curious to know if BoostrapVueNext is getting enough focus to have a stable release before Vue 2 reaches EOL in December of this year, which, of course, includes Vue 2.7. I'd love to keep pluggin' away using BootstrapVue, but if a stable Vue 3 version isn't going to be released until long after Vue 2 reaches EOL, I'm afraid I'll need to begin considering alternative options for my personal apps. However, I do love the BootstrapVue project and would prefer to stick w/ it! <3

[VividLemon]

Question. As I'd Love to stick w/ Bootstrap-Vue, I'm curious to know if BoostrapVueNext is getting enough focus to have a stable release before Vue 2 reaches EOL in December of this year, which, of course, includes Vue 2.7. I'd love to keep pluggin' away using BootstrapVue, but if a stable Vue 3 version isn't going to be released until long after Vue 2 reaches EOL, I'm afraid I'll need to begin considering alternative options for my personal apps. However, I do love the BootstrapVue project and would prefer to stick w/ it! <3

If one believes a project isn't receiving enough attention, what's stopping them from contributing themselves?

It will be available before eol. All that remains is compatibility fixes and various bugfixes. As well as a refactor of the Table component, which I will handle myself.

[eramosr16]

TL;DR (last update: Oct 25, 2022)

white_check_mark v.2.23.0 with initial support of Vue.js 3 released tada

Next steps:

* [ ]  Publish initial rewrite infrastructure (includes CI, automated comparison of render output with `v2.23.0`)

* [ ]  Rewrite each components one by one and reach feature parity with `v2.23.0`

* [ ]  Explore Bootstrap v5 compatibility

Longer version

Bootstrap-Vue is heading towards Vue.js 3. Our main goals remain the same:

* we do not want to introduce as few breaking changes as possible (ideally 0). We respect our existing users and understand that Vue2 -> Vue3 migration is already quite painful so we do not want to add extra one

* we want to migrate to TypeScript, Vite and SFC for Vue.js 3 to simplify contributions to this project

* migration to Bootstrap v5 is definitely on the priority list but right after previous step

I will keep you posted on updates
Original description from December 2021

TL; DR

Any updates?, we are on April 2023

[jeffsta9]

If one believes a project isn't receiving enough attention, what's stopping them from contributing themselves?

It will be available before eol. All that remains is compatibility fixes and various bugfixes. As well as a refactor of the Table component, which I will handle myself.

@VividLemon I appreciate your response and the confirmation on the timeline of the initial production release. TBH, I simply haven't had confidence that this was truly going to pull together at all, let alone before Vue 2 EOL. However, I'm thrilled to hear that it is, indeed, intended to be pushed out before then. And I will certainly be more than happy to contribute whatever I can. I am starting a rebuild of a Vue 2.7 / Nuxt-Bridge project from scratch within Nuxt 3 and will be using bootstrap-vue-next as the previous build was w/ bootstrap-vue. I will be sure to submit PRs for any issues I encounter that I feel confident in resolving :)

[HoldenCreative]

On that note of contributing @xanf et al. - where can all of us who support BV and appreciate your hard work despite the ongoing war, make a financial contribution?

[VividLemon]

If one believes a project isn't receiving enough attention, what's stopping them from contributing themselves?
It will be available before eol. All that remains is compatibility fixes and various bugfixes. As well as a refactor of the Table component, which I will handle myself.

@VividLemon I appreciate your response and the confirmation on the timeline of the initial production release. TBH, I simply haven't had confidence that this was truly going to pull together at all, let alone before Vue 2 EOL. However, I'm thrilled to hear that it is, indeed, intended to be pushed out before then. And I will certainly be more than happy to contribute whatever I can. I am starting a rebuild of a Vue 2.7 / Nuxt-Bridge project from scratch within Nuxt 3 and will be using bootstrap-vue-next as the previous build was w/ bootstrap-vue. I will be sure to submit PRs for any issues I encounter that I feel confident in resolving :)

Generally the smaller issues described exist in things like todo comments in the actual project or appear as "compatibility issues", where there isn't any formal issue, but there existing a difference between bootstrap-vue and bootstrap-vue-next. (Say, if we didn't include a prop by accident).

On thing that needs to occur before v1.0 is a comparison between the two libraries. To go through each component and create a list on a prop, event, or slot that does not match the bootstrap-vue implementation.

An excel list that covers these two things would be a significant help to alleviate some of the tedious work off of myself. In which case I can use the list to implement missing features, or describe them in the breaking changes list.

Most of the issues on the repository are somewhat complicated. But occasionally you can get stuff like bootstrap-vue-next/bootstrap-vue-next#215 that are fairly simple additions, but I just haven't put in the time to fix.

On that note of contributing @xanf et al. - where can all of us who support BV and appreciate your hard work despite the ongoing war, make a financial contribution?

Afaik, Illya does not have any official funding links. I 'think' he has access to pull funds out of the opencollective. But he has never taken any funding -- nor has anyone in multiple years. So, make of this what you will.

[HoldenCreative]

Afaik, Illya does not have any official funding links. I 'think' he has access to pull funds out of the opencollective. But he has never taken any funding -- nor has anyone in multiple years.

Understood. We're not contributing code so I'd like to do something. I'll stand by for more info/updates.

[IgorSushko1]

Hi all! We are starting to migrate the project to Nuxt3, but I would like to keep bootstrap-vue. The package shows that the stable version of bootstrap-vue-next has not yet been released. Hence the question arises: does the project have any support at all, and does the team have the strength to develop and support the project?

[uykusuz]

@IgorSushko1

See this comment

[IgorSushko1]

@IgorSushko1

See this comment

I saw, version of bootstarp-vue-next is 0.15. Was publish 2 month ago :( and i don't know should I use bootstrap-vue-next now or another library/

[xmatthias]

Using bootstrap-vue-next since quite some time now - and i must say, i'm pretty happy.

Bug reports (the few i found) are usually quickly addressed, and most functionality (i need) is available and functional.