Vue 2.5.1: Invalid value for option "components": expected an Object, but got Array.
See original GitHub issueAfter upgrading to Vue 2.5.1 I receive the following console warning:
Triggered by bootstrap-vue.esm.js:
// Register components
for (var component in components) {
Vue.component(component, components[component]);
}
Issue Analytics
- State:
- Created 6 years ago
- Reactions:23
- Comments:31 (12 by maintainers)
Top Results From Across the Web
Avoid warning "Invalid value for option components" - Get Help
It works fine, but in the console I get the following warning: [Vue warn]: Invalid value for option "components": expected an Object, but...
Read more >[Vue warn]: Invalid prop: type check failed for prop "value ...
I have an input with the type number, ...
Read more >type check failed for prop "value". expected array, got object ...
I'm receiving the following error: [Vue warn]: Invalid prop: type check failed for prop "value". Expected Object, got Number. @Component({ ...
Read more >Creating a GraphQL Client With the Vue.js Framework
... bug that causes an error ( Invalid value for option "components": expected an Object, but got Array ) on the 2.5.x version...
Read more >Forms - Vue Formulate
You can read and write to form values using v-model just as you would on an ... are passed an object of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Until fix is released, I worked around it using:
putting together @kriomant and @Flygenring code, here is a complete workaround for Node, works for me on the entire bootstrap-vue import: