\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nconsole output:\r\n```sh\r\n[Vue warn]: Failed to resolve component: IconIcones 21:27:18\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```\n\n### Additional context\n\nThe above example works in Nuxt 3.4.x\n\n### Logs\n\n_No response_",[2025,2026,2029],{"name":2016,"color":2017},{"name":2027,"color":2028},"bug","d73a4a",{"name":2030,"color":2031},"🔨 p3-minor","FBCA04",20937,"Regression: Cannot resolve component if its folder's name is a prefix of the component's name","2023-05-19T11:23:25Z","https://github.com/nuxt/nuxt/issues/20937",0.6399734,{"labels":2038,"number":2045,"owner":1985,"repository":1985,"state":1995,"title":2046,"updated_at":2047,"url":2048,"score":2049},[2039,2040,2043],{"name":2016,"color":2017},{"name":2041,"color":2042},"pending triage","E99695",{"name":2044,"color":2031},"needs reproduction",13746,"nuxt-link does not resolve inside an as prop","2025-02-07T21:30:33Z","https://github.com/nuxt/nuxt/issues/13746",0.64975923,{"description":2051,"labels":2052,"number":2055,"owner":1985,"repository":1985,"state":1995,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Environment\n\nNuxi 3.2.2 \r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.14.1`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `components`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nReproduce Link: https://stackblitz.com/edit/github-tznxrd\r\n\r\n1. npx nuxi init demo\r\n2. cd demo\r\n3. npm install\r\n4. mkdir -p components/layouts\r\n5. edit nuxt.config.ts\r\n **nuxt.config.ts**\r\n ```\r\n export default defineNuxtConfig({\r\n components: [\r\n { path: '~/components/layouts', prefix: 'Special' },\r\n '~/components'\r\n ]\r\n })\r\n ```\r\n\r\n\r\n6. create **header.vue** under components/layouts\r\n ```\r\n \u003Ctemplate>\r\n \u003Cdiv>\r\n Header\r\n \u003C/div>\r\n \u003C/template>\r\n ```\r\n\r\n7. import header.vue in **app.vue**\r\n ```\r\n \u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CHeader />\r\n \u003CNuxtWelcome />\r\n \u003C/div>\r\n \u003C/template>\r\n \r\n \u003Cscript>\r\n import Header from '~/components/layouts/header.vue';\r\n \u003C/script>\r\n ```\r\n\r\n\r\n8. npm run dev\r\n\n\n### Describe the bug\n\n[Vue warn]: Failed to resolve component: Header\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2053,2054],{"name":2016,"color":2017},{"name":2041,"color":2042},19310,"If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.","2023-02-27T12:15:17Z","https://github.com/nuxt/nuxt/issues/19310",0.6532979,{"description":2061,"labels":2062,"number":2069,"owner":1985,"repository":1985,"state":1995,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: extends, modules, devtools, app, runtimeConfig, future, compatibilityDate, telemetry, eslint\n- Runtime Modules: @nuxt/ui@2.21.0, @nuxt/eslint@1.0.1, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-qmxnxe9n?file=app.vue\n\n### Describe the bug\n\nHi,\n\nI've encountered a component resolution issue in Nuxt.\n\nWhen a component folder is named using PascalCase (e.g., TicketList) and contains a component named `List.vue` (as a child), Nuxt fails to resolve `List.vue`. It seems that because \"List\" is the latter part of the folder name, Nuxt does not correctly recognize `List.vue` as a separate component.",[2063,2066],{"name":2064,"color":2065},"workaround available","11376d",{"name":2067,"color":2068},"dx","C39D69",31052,"File Based Routing Naming Collision","2025-02-22T22:30:10Z","https://github.com/nuxt/nuxt/issues/31052",0.6618062,{"description":2075,"labels":2076,"number":2085,"owner":1985,"repository":1985,"state":1995,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-nbj7gc?file=components/ItemHolder/ItemHolder.vue\n\n### Describe the bug\n\ncomponents/ItemHolder/Item/Item.vue gets incorrectly resolved to Item\r\nwhile\r\ncomponents/ItemHolder/Item1/Item1.vue correctly resolves to ItemHolderItem1\r\n\r\nThe problem is that here https://github.com/nuxt/nuxt/blob/8b86d39e30ca970fb0adf2b5665a77f8dbbfb439/packages/nuxt/src/components/scan.ts#L85 adding segments prematurely terminates because\r\ncomponents/ItemHolder\r\ngets treated like\r\ncomponents/Item/Holder\r\nwould. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2077,2080,2081,2082,2083],{"name":2078,"color":2079},"good first issue","fbca04",{"name":2016,"color":2017},{"name":2027,"color":2028},{"name":2030,"color":2031},{"name":2084,"color":2079},"✨ good reproduction",20613,"Component name resolution is broken in some cases","2023-05-15T12:34:05Z","https://github.com/nuxt/nuxt/issues/20613",0.66215074,["Reactive",2091],{},["Set"],["ShallowReactive",2094],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"DspzUQtcXLnbRzl4cbxsVVDHmas-lRQ65ekGezcaiyc":-1},"/nuxt/nuxt/12304"]