Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown custom element: <sweet-modal> #22

Closed
packytagliaferro opened this issue Jun 21, 2017 · 8 comments
Closed

Unknown custom element: <sweet-modal> #22

packytagliaferro opened this issue Jun 21, 2017 · 8 comments
Labels

Comments

@packytagliaferro
Copy link

For some reason this stopped working today.

App.js:

import { SweetModal, SweetModalTab } from 'sweet-modal-vue'

Vue.component('SweetModal', SweetModal);

const app = new Vue({
    el: '#app',
});

php file:


<sweet-modal ref="wodModal">

      <wod-new></wod-new>

</sweet-modal>
@packytagliaferro
Copy link
Author

packytagliaferro commented Jun 21, 2017

I have also tried:

Vue.component(SweetModal);
and

const app = new Vue({
    el: '#app',
     components:{
	SweetModal
      }
});

@bluefirex
Copy link
Member

bluefirex commented Jun 22, 2017

The last approach is the correct one. What's the exact error you get?

@Sopamo
Copy link

Sopamo commented Jun 22, 2017

Seems like this is a bug introduced in 1.1.1. I downgraded to 1.1.0, that fixed the problem.

@packytagliaferro
Copy link
Author

I just ended up using Vue.component(SweetModal); in my app.js file above my vue instance with my other components and then downgraded and it seemed to work.

The error was:

Unknown custom element: <sweet-modal> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

@dubcanada
Copy link

Getting this same error with the latest sweetmodal, was fine with 1.1.0

@Fleeck
Copy link

Fleeck commented Jun 27, 2017

Same thing here. Everything worked before upgrading to 1.1.1, downgrade fixes the problem. Probably there's something wrong with imports.

@Dmitry1987
Copy link

same here, 1.1.0 doesn't cause this error

@bluefirex
Copy link
Member

bluefirex commented Jul 2, 2017

Temporarily fixed in d0c9f3f, released in v1.1.2

Thanks to everyone for reporting it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

6 participants