\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_",[2916,2917,2918],{"name":2882,"color":2883},{"name":2894,"color":2895},{"name":2919,"color":2920},"🔨 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.66345483,{"description":2927,"labels":2928,"number":2930,"owner":2869,"repository":2869,"state":2885,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Environment\n\n2 Nuxt Applications with same Environment:\n\nnuxt: 3.14.1592\nnitro: 2.10.4\n\n### Reproduction\n\nLink: https://stackblitz.com/edit/nuxt-starter-tckmhw?file=base%2Fnuxt.config.ts\n\nSteps: \n\n- `cd layer` \n- `yarn` or `npm i` \n- `yarn dev` or `npm run dev`\n\n### Describe the bug\n\nWhen working with two Nuxt applications, one as a base and the other as a layer, there is an issue with component exports from the base application to the layer.\n\n**Here’s the scenario:**\n\n- The base application contains components, which are intended to be imported and used in the layer application.\n- In the layer application, the base application is extended using the `extend` property in `nuxt.config.ts`.\n- The base application uses a nested component structure. To simplify usage, we disabled component name prefixes by setting `pathPrefix: false` in the `nuxt.config.ts` as per the [official documentation](https://nuxt.com/docs/guide/directory-structure/components).\n- After doing this, components from the base application are no longer exported to the layer application, making them inaccessible.\n\n**Conclusion:** This behavior breaks the expected functionality where components from the base application should be seamlessly available in the layer application. It appears that the configuration in the base application's nuxt.config.ts is interfering with the component export mechanism.\n\nAnd also this issue might not be limited to the `pathPrefix` setting. It could also occur if the base application has custom `components` property and with related configurations in it's `nuxt.config.ts`. \n\n\n### Logs\n\n```shell-script\nWARN [Vue warn]: Failed to resolve component: TestInner\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CApp> \n at \u003CNuxtRoot>\n```",[2929],{"name":2866,"color":2867},30099,"Nuxt Layers: `pathPrefix: false` prevents component imports when the application is extended","2024-12-02T13:23:12Z","https://github.com/nuxt/nuxt/issues/30099",0.6697002,{"labels":2936,"number":2939,"owner":2869,"repository":2869,"state":2885,"title":2940,"updated_at":2941,"url":2942,"score":2943},[2937,2938],{"name":2882,"color":2883},{"name":2866,"color":2867},13972,"Global components per-directory setting not working properly","2023-01-19T17:11:06Z","https://github.com/nuxt/nuxt/issues/13972",0.6705296,{"description":2945,"labels":2946,"number":2951,"owner":2869,"repository":2869,"state":2885,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.6.2\r\n- Nitro Version: 2.5.2\r\n- Package Manager: pnpm@8.4.0\r\n- Builder: vite\r\n- User Config: nitro, typescript, runtimeConfig, devServerHandlers, modules, app, postcss, routeRules, i18n, schemaOrg, delayHydration, vite\r\n- Runtime Modules: nuxt-delay-hydration@1.2.1, nuxt-schema-org@2.2.0, @nuxtjs/i18n@8.0.0-beta.10\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-jaeoi1?file=components%2Ffoo.vue\n\n### Describe the bug\n\nHi,\r\n\r\nAfter upgrade to 3.6.2 : \r\n\r\n**After building** the application (no problem in dev) :\r\n\r\nThe icon's url in the inlined css is ok : \r\n```\r\n[data-icon=foo] {\r\n --icon-custom: url(/_nuxt/ic-ecurie.dfbfbb0a.svg);\r\n}\r\n```\r\n\r\nThe icon's url in the **entry.css gives a 404**\r\n```\r\n[data-icon=foo] {\r\n --icon-custom: url(./ic-ecurie.dfbfbb0a.svg);\r\n}\r\n```\r\n\r\nThere's no `_nuxt` in the url because the asset is in the same directory as the css but the browser consider it not and resolve with his path.\r\n\r\n\r\nMaybe i make something wrong but I see no problems in Nuxt 3.5.3 :thinking: \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2947,2948,2949],{"name":2882,"color":2883},{"name":2866,"color":2867},{"name":2950,"color":2920},"needs reproduction",22086,"Bad path of assets after 3.6 upgrade","2023-07-19T06:47:37Z","https://github.com/nuxt/nuxt/issues/22086",0.67067224,{"description":2957,"labels":2958,"number":2966,"owner":2869,"repository":2869,"state":2885,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.17.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: pnpm@10.9.0\n- Builder: -\n- User Config: compatibilityDate, future, components, imports, typescript, css, vite, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\n1. Components documentation: https://nuxt.com/docs/guide/directory-structure/components#:~:text=throughout%20your%20application.-,export%20default%20defineNuxtConfig(%7B,%7D),-You%20can%20also\n2. Imports documentation: https://nuxt.com/docs/guide/directory-structure/composables#:~:text=export%20default%20defineNuxtConfig,%7D)\n\n### Describe the bug\n\nHello 👋,\n\nThere seems to be an inconsistency in how paths are resolved between the components.dirs and imports.dirs configuration options in the Nuxt config.\n\nSpecifically:\n\t•\tcomponents.dirs requires a relative path from the project root, prefixed with ~ to be relative to the app directory.\n\t•\timports.dirs uses a relative path from the app directory, but does not require the ~ prefix.\n\n```ts\nexport default defineNuxtConfig({\n components: {\n dirs: [\n '~/ui/components', // requires '~'\n ],\n },\n\n imports: {\n dirs: [\n 'ui/composables', // works without '~'\n ],\n },\n})\n```\n\nThis discrepancy can be confusing and may lead to misconfigurations or the assumption that both behave the same way. It would be helpful to either unify the path handling or provide clearer documentation highlighting the difference.\n\nThanks!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2959,2960,2963],{"name":2879,"color":2880},{"name":2961,"color":2962},"good first issue","fbca04",{"name":2964,"color":2965},"🍰 p2-nice-to-have","0E8A16",31988,"Inconsistent Path Resolution Between components.dirs and imports.dirs in Nuxt Config","2025-05-17T16:52:20Z","https://github.com/nuxt/nuxt/issues/31988",0.6728977,{"description":2972,"labels":2973,"number":2976,"owner":2869,"repository":2869,"state":2885,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Environment\n\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `pnpm@7.22.0`\r\n- Builder: `vite`\r\n- User Config: `telemetry`, `test`, `srcDir`, `css`, `ignore`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-ywawgt?file=.nuxt/components.d.ts\n\n### Describe the bug\n\nWhen using components organized within folders, Nuxt is adding non-component files to the global components list. \n\n### Additional context\n\n1. I have tested using the default `ignore` options\r\n2. I have tested by setting explicit `ignore` options\r\n3. I have tested using the `-` prepend method\r\n\r\nNone seem to work for me currently.\r\n\r\n> Also FYI these files being present seem to prevent the `build` command from working on my machine. Could not reproduce this on Stackblitz, but provided my logs below.\n\n### Logs\n\n```shell-script\n➜ pnpm run build\r\n\r\n> @ build /Users/REDACTED\r\n> nuxt build\r\n\r\nNuxi 3.0.0 08:02:07\r\nNuxt 3.0.0 with Nitro 1.0.0 08:02:07\r\n\r\n ERROR 'promises' is not exported by __vite-browser-external, imported by ../chia/node_modules/.pnpm/local-pkg@0.4.3/node_modules/local-pkg/dist/shared.mjs\r\nfile: /Users/REDACTED/node_modules/.pnpm/local-pkg@0.4.3/node_modules/local-pkg/dist/shared.mjs:61:13\r\n59: import process2 from \"process\";\r\n60: import path from \"path\";\r\n61: import fs, { promises as fsPromises } from \"fs\";\r\n ^\r\n62: import { fileURLToPath } from \"url\";\r\n\r\n\r\n ERROR 'promises' is not exported by __vite-browser-external, imported by ../chia/node_modules/.pnpm/local-pkg@0.4.3/node_modules/local-pkg/dist/shared.mjs\r\n\r\n at error (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:1858:30)\r\n at Module.error (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:12429:16)\r\n at Module.traceVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:12788:29)\r\n at ModuleScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:11440:39)\r\n at FunctionScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)\r\n at ChildScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)\r\n at MemberExpression.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:8601:49)\r\n at ConditionalExpression.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:5269:23)\r\n at VariableDeclarator.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:5269:23)\r\n at VariableDeclaration.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:5265:73)\r\n\r\n ELIFECYCLE Command failed with exit code 1.\n```\n",[2974,2975],{"name":2882,"color":2883},{"name":2866,"color":2867},18439,"nuxt.config's `ignore` and `ignore-prefix` not working","2023-01-23T06:45:32Z","https://github.com/nuxt/nuxt/issues/18439",0.67323244,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9iLZvtT8f3kihyVXDG50SJtcjrpn7EGDLuUcj3UcsQ8":-1},"/nuxt/nuxt/18986"]