-
Notifications
You must be signed in to change notification settings - Fork 42
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: <masonry> #15
Comments
Thanks for reporting Chase. Are you on the latest version of vue? If so,
I'll work in a fix in the coming days
…On Fri, Aug 17, 2018 at 8:23 AM Chase ***@***.***> wrote:
When using masonry as described in the README I get the following error:
Unknown custom element: <masonry> - did you register the component
correctly? For recursive components, make sure to provide the "name" option.
It does work, however. I just would like to remove those errors from the
console.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#15>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AB0Qhl5rpjoszqsXFEdqvOxDfKwuiuwVks5uRuAJgaJpZM4WBwLX>
.
|
Yes I am, thank you! Also, any chance you can look at #14 ? |
I havn't been able to reproduce this error Chase. I've tried masonry across the latest vue-cli project build, via script and all seems to be working ok. Still doesn't mean I havn't missed something. Stackoverflow suggests this issue could be due to registering the plugin |
Hi @paulcollett , I'm trying to get masonry to work with Nuxt (Duplicate of #19) I don't know, what I'm missing... I just registered the plugin as David wrote. Can you please help me to get this working? I'm moving from my vue.js app to Nuxt and want to keep this component... |
When using masonry as described in the README I get the following error:
Unknown custom element: <masonry> - did you register the component correctly? For recursive components, make sure to provide the "name" option.
It does work, however. I just would like to remove those errors from the console.
The text was updated successfully, but these errors were encountered: