nuxt: Cannot read property 'props' of undefined
Version
Reproduction link
Steps to reproduce
An upgrade from 2.12.0 to 2.12.1 leads to this error.
I somewhat ‘traced’ the error and I think it has something todo with templates?
It crashed in the normalizeProps function
function normalizeProps (options, vm) {
var props = options.props;
.nuxt/App.js
const layouts = { "_clean": sanitizeComponent(_77263413),"_default": sanitizeComponent(_6f6c098b),"_default/footer": sanitizeComponent(_5b8eca9f),"_login": sanitizeComponent(_77a66d33),"_simple": sanitizeComponent(_ee7125b0) }
What is expected ?
Working like version 2.12.0
What is actually happening?
Error
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 11
- Comments: 25 (1 by maintainers)
As the error message suggests, it’s inferring an invalid name. This can be fixed giving a custom name to the component.
For example to
layouts/default.vueI am using nuxt-vuetify template. I am getting this same warning (not every time but often) when I click on select components e.g. v-select or v-autocomponent.
Hei @pi0
thanks for support, but unfortunately the problem persists even with
v2.12.2😦I’m having this in my console:
Maybe is because I’m using kind of dynamic layouts based on route. I made a post about this where you can see my code:
https://dev.to/alligatore3/nuxt-js-dynamic-layouts-by-current-route-3jl1
+1 At the same time i got error
ERROR [Vue warn]: Invalid component name: "_2d21d098". Component names should conform to valid custom element name in html5 specification.in server consoleYes, as @IvanArjona said.
UPDATE: One of my first issues were caused by WebStorm since when you right-click to create a new Vue component and, let’s suppose, we create a new dynamic page, WS will automatically create a name with that underscore. At first I didn’t recognize it.
Getting this error in v2.14.0…
Invalid component name: "layouts/default.vue". Component names should conform to valid custom element name in html5 specification.Any update or workaround?
Same here.
In my case, I just remove
in nuxt.config.js, It works.
Try add any name to default layout, how message say to you =)
It’s work for me
@ram-you Yes, you’re right, I just point it out the relation with
build.splitChunks.layoutsbut not solved the problem, only for investigating purpose.It’s seems like PR #7128 and here leads this problem, any ideas?
@MLDMoritz I think this should be handled internally by Nuxt itself.
@pi0 @Alligatore3 I have the same issue and I am not using dynamic layouts based on route