feat(nuxt): warn when components have a name conflict #27838
Conversation
|
|
There was a problem hiding this comment.
Instead, if you update L96 as follows:
- const pascalName = pascalCase(componentNameSegments)
const pascalName = pascalCase(componentNameSegments).replace(/^Lazy(?=[A-Z])/, '')then this is what will be logged:
WARN Two component files resolving to the same name Bob: 11:49:28 AM
- /Users/daniel/code/nuxt/nuxt/playground/components/LazyBob.vue
- /Users/daniel/code/nuxt/nuxt/playground/components/Bob.vue
That feels like a good approach, and it's an even more minimal change.
|
How about files that don't have a a non-lazy counterpart? |
|
Hm - yes, it's probably worth over-warning, but it's most helpful when we can point to the component it would collide with. either way, it shouldn't just be about the component file name but the resolved component name. So |
|
Ah, I see. Yea, that is true, the warning will also need to be modified for it |
🔗 Linked issue
closes #27800
📚 Description
This PR warns the user when a component is found with name conflicts that use the reserved Lazy prefix