-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 for Layout #1426
Comments
Don't use words like sometimes. You should tell us how. If the situation you mentioned only occurs after modifying |
@shigma It's why it was actually emphasized, and why there is a mention:
It was on purpose to tell you that I have no idea of the why or how. But now you told me that it can be after updating 😉 |
A new component added in |
In my case, the issue was simply a hanging comma in the config file. Very strange. |
… />` in a custom page without markdown (#1699) **Bug**: example, , will raise `[Vue warn]: Unknown custom element`, like #1173 #1426 **Reason**: because it not inject any content in `@internal/page-components` while not find markdown file, `Vue.component` of `pageKey` must be `undefined`, then `h(pageKey)` raise this error **Fix**: judge as `if (Vue.component(pageKey))`, unnecessary to render if no component existed
I still can have the issue in Vuepress v1.9.7. I even tried the Vuepress docs codebase and same problem. [Vue warn]: Unknown custom element: <v-7324b362> - did you register the component correctly? For recursive components, make sure to provide the "name" option. |
@bill-dou have you gotten some help on this? |
@krofax yes, I got a solution. EnhanceApp.js
|
Bug report
Version
v1.0.0-alpha.44
Steps to reproduce
What is expected?
A new component in
theme/layouts
directory should be available as layout.What is actually happening?
Sometimes when navigating through the app, a page is not loaded, and an "Unknown custom element" error is thrown.
It can be a custom layout or not.
The page is ok if I refresh it.
It don't know how to reproduce the bug and find a proper pattern for that.
Other relevant information
I'm using the blog plugin, and it adds some layout automatically to pages.
All my Layout components have a name key.
The text was updated successfully, but these errors were encountered: