[Vue warn]: Unknown custom element: <swiper> - did you register the component correctly? For recursive components, make sure to provide the "name" option.
See original GitHub issueVue.js version and component version
“vue”: “^2.5.9”, “vue-awesome-swiper”: “^3.0.0”,
Steps to reproduce
- Update to latest Vue-Awesome-Swiper using Swiper 4
- Mount with component using the example in SPA
What is Expected?
Display the swiper (carousel) component
What is actually happening?
Error being shown:
[Vue warn]: Unknown custom element: <swiper>
- did you register the component correctly? For recursive components, make sure to provide the “name” option.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
did you register the component correctly? For recursive ...
From the error, what I can say is you have not defined the name in your component Tabpane . Make sure to verify...
Read more >How to Solve "Unknown Custom Element" in Vue
[Vue warn]: Unknown custom element: - did you register the component correctly? For recursive components, make sure to provide the "name" option.
Read more >Solution to Vue.js Error - Unknown custom element - did you ...
I'm building a recursive Vue.js component and ran into this error: Unknown custom element: - did you register the component correctly?
Read more >Did you register the component correctly? For recursive ...
Hello, i making a recursive thing an i get this error : [Vue warn]: Unknown custom element: <MultiPaneBox> - did you register the...
Read more >报错[Vue warn]: Unknown custom element: - did you register ...
For recursive components, make sure to provide the “name” option. 在这里插入图片描述. 分析. 出现这种问题的原因我目前只遇到一种,那就是vue的组件 ...
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
I will fix it in v3.0.1 .