@milenon Hi. thanks for your interest in future of this project. Actually I (and other devs) think that maybe it could be better to keep bootstrap-vue as minimal as possible and try to have best quality standard bootstrap components. This is for keeping dists as clean and small as possible. Anyway, i'm okay with adding some extra components bundled in a different js. (Specially about date-time pickers and a more feature-rich table component) So we can for example include bootstrap-vue/dist/bootstrap-vue.extra to have more components like <b-date-picker> :))

cc @bootstrap-vue/dev What's your idea?

The package should just do Bootstrap things but in Vue. It should not exceed Bootstrap's functionality except for where it makes sense because of the marginal resource/effort cost on account of the introduction of Vue. The main example here is providing reactivity to property inputs, which doesn't happen quite as magically with Bootstrap and jQuery. Extra fun things could be in a separate package which pulls this in as a dependency.

The key concept here is separation of concerns. If this package tries to do everything well, then it will do nothing well. And it will be bloated.

My own little toy project is an example of this, which depends on Popover.
https://github.com/SirLamer/click-confirm

I use this package for a date picker in my project:
https://github.com/vuwe/vue-flatpickr

Fully agree with @SirLamer. Main purpose of this project is to extend Bootstrap 4 components with reactivity) Additional features can take a place, but in separate project).

Reasonable! I Agree Too :))