The global name being window.bootstrapVue is a legacy name (been htat way since before I started with the project), although we may consider adding in a PascalCase version (create both for backwards compatability). Although installing as a property on global isn't really required, as BootstrapVue (when used in browser script tags) will auto install itself via the Vue global.

Vue supports both object and function for plugins, and Vue's doc's actually provide examples in the object format: https://vuejs.org/v2/guide/plugins.html#Writing-a-Plugin

Object and Function as plugins are acceptable to Vue. so I don't see a need to change from passing Function vs Object as the plugin (an the former actually has benefits when creating the CommonJs bundle version)

#3850 looks good, thank you

@Andrei-Pozolotin Note that VueRouter is also a constructor function (technically it is a class creator), for creating a router instance to pass to an app. While it is a function, Vue, when one does Vue.use(VueRouter), sees it an an Object with an install property (functions and classes in JavaScript are actually based on the Object prototype).

Vue first inspects the passed plugin as an Object and looks for an install property, and if found executes it, otherwise if it sees the plugin as a Function without an install property it assumes the function is the installer (which it is not in the case of VueRouter)

The BootstrapVue plugin is not a constructor (one doesn't use foo = new BootstrapVue()), hence it is a plugin Object with an install property.

So to your point number 3, it is not leading to endless confusion (if one understands Vue's internals).

ok, clear, thank you