\r\n\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\ndefineProps({ icon: String })\r\n\u003C/script>\r\n```",[],174,"closed","Can the Base component be changed to \"NuxtIcon\" instead of \"Icon\" with the \"name\" attribute?","2024-06-26T16:45:07Z","https://github.com/nuxt/icon/issues/174",0.60013324,{"description":3045,"labels":3046,"number":104,"owner":3020,"repository":3021,"state":3039,"title":3050,"updated_at":3051,"url":3052,"score":3053},"I know `\u003CIcon>` is much sexier than `\u003CNuxtIcon>` or `\u003CNIcon>` but maybe in order to avoid conflicting we can prefix component name too?",[3047],{"name":3048,"color":3049},"enhancement","a2eeef","Using two part component name","2022-09-07T13:21:28Z","https://github.com/nuxt/icon/issues/3",0.6383519,{"description":3055,"labels":3056,"number":3057,"owner":3020,"repository":3021,"state":3039,"title":3058,"updated_at":3059,"url":3060,"score":3061},"Although it looks redundant, Iconify uses `\u003CIcon icon=\"...\" />` as the Vue component. Since this module uses Iconify, why not keeping the same structure so we can just copy the component from their lib? An alias prop would be welcomed if I'm sounding too radical 😋 That way we can use both `name` and `icon`.",[],51,"[question] Why not using `icon` as a prop instead of `name`?","2023-02-16T15:53:34Z","https://github.com/nuxt/icon/issues/51",0.7043463,{"description":3063,"labels":3064,"number":3071,"owner":3020,"repository":3020,"state":3039,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.8.2`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.0`\r\n- Package Manager: `pnpm@8.10.5`\r\n- Builder: `-`\r\n- User Config: `runtimeConfig`, `site`, `modules`, `experimental`, `sourcemap`, `devtools`, `app`, `typescript`, `vite`, `nitro`, `css`, `postcss`, `image`, `content`, `colorMode`, `plausible`, `sitemap`, `ogImage`\r\n- Runtime Modules: `@nuxt/content@2.9.0`, `@nuxt/image@1.1.0`, `@nuxtjs/color-mode@3.3.2`, `@nuxtjs/plausible@0.2.3`, `@nuxtseo/module@2.0.0-beta.45`, `@unocss/nuxt@0.57.7`, `@vueuse/nuxt@10.6.1`, `nuxt-icon@0.6.6`, `nuxt-vitest@0.11.5`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nSee description.\n\n### Describe the bug\n\nIn `v0.6.5` this works:\r\n\r\n```ts\r\nnuxtIcon: {\r\n aliases: {\r\n 'aws': 'IconAWS',\r\n // ...\r\n }\r\n}\r\n```\r\n\r\nif there is a component in global named `IconAWS.vue`, but in `v0.6.6` it breaks. The reason is the uppercase naming, if I rename the component and the alias to `IconAws.vue` it works.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3065,3068],{"name":3066,"color":3067},"3.x","29bc7f",{"name":3069,"color":3070},"pending triage","E99695",24420,"v0.6.6 has problems with uppercase alias names","2023-11-23T00:10:37Z","https://github.com/nuxt/nuxt/issues/24420",0.7051534,{"description":3077,"labels":3078,"number":3079,"owner":3020,"repository":3021,"state":3039,"title":3080,"updated_at":3081,"url":3082,"score":3083},"Hi,\n\nI’ve searched high and low and didn’t find this covered anywhere, apologies if this has been addressed already.\n\nI am using @nuxt/icon with @iconify and the VS Code Intellisense plugin, works great.\n\nI have a custom component that I would like to pass autocompleted string values to, something like:\n\n```html\n\u003CHighlight\n icon-name=\"...\"\n\u003C!-- ^ This should suggest values such as \"bxs:success\" etc, same as the \u003CIcon> component directly -->\n```\n\nI tried this:\n\n```ts\n// Highlight.vue\n\nimport type { ExtractPublicPropTypes } from 'vue';\nimport { Icon } from '#components';\ntype IconName = ExtractPublicPropTypes\u003Ctypeof Icon['name']>\n\nconst props = defineProps\u003C{\n iconName: IconName\n}>()\n```\n\nI get a vague `{} & {}` as the resulting type. Any help appreciated!",[],412,"Infer \u003CIcon> \"name\" as prop to be used in a custom component","2025-07-02T09:24:15Z","https://github.com/nuxt/icon/issues/412",0.70555145,{"description":3085,"labels":3086,"number":659,"owner":3020,"repository":3021,"state":3039,"title":3087,"updated_at":3088,"url":3089,"score":3090},"Is it possible to change the `/components/global` directory. I have checked the code of this module, but it seems to me that it could be something that's inside Nuxt 3?\r\n\r\nProposition:\r\n```js\r\n nuxtIcon: {\r\n size: \"16px\",\r\n source: '~/components/icons' // or an array with multiple values\r\n },\r\n```",[],"Feature: Possible to change the icons directory","2023-01-19T16:59:35Z","https://github.com/nuxt/icon/issues/18",0.7093769,{"description":3092,"labels":3093,"number":3094,"owner":3020,"repository":3021,"state":3039,"title":3095,"updated_at":3096,"url":3097,"score":3098},"Installed following the steps [here](https://nuxt.com/modules/icon).\r\n```\r\nnpm install --save-dev nuxt-icon\r\n```\r\nAdded to my `nuxt.config.ts`\r\n```\r\n modules: [\r\n // https://go.nuxtjs.dev/bootstrap\r\n 'bootstrap-vue/nuxt',\r\n // https://go.nuxtjs.dev/pwa\r\n '@nuxtjs/pwa',\r\n // https://go.nuxtjs.dev/content\r\n '@nuxt/content',\r\n // https://nuxt.com/modules/icon\r\n 'nuxt-icon'\r\n ],\r\n```\r\nUsed on a component\r\n```\r\n\u003CIcon name=\"logos:instagram-icon\" />\r\n```\r\n\r\nThe page rendered without the icon and got this on the console.\r\n```\r\n[Vue warn]: Unknown custom element: \u003CIcon> - did you register the component correctly? For recursive components, make sure to provide the \"name\" option.\r\n\r\nfound in\r\n\r\n---> \u003CLayouts/default.vue> at layouts/default.vue\r\n \u003CRoot>\r\n```\r\n\r\n### My dependencies\r\n```\r\n \"dependencies\": {\r\n \"@nuxt/content\": \"^1.0.0\",\r\n \"@nuxtjs/pwa\": \"^3.3.5\",\r\n \"bootstrap\": \"^4.6.2\",\r\n \"bootstrap-vue\": \"^2.22.0\",\r\n \"bootswatch\": \"^5.2.3\",\r\n \"core-js\": \"^3.25.3\",\r\n \"nuxt\": \"^2.15.8\",\r\n \"nuxt-icon\": \"^0.4.0\",\r\n \"vue\": \"^2.7.10\",\r\n \"vue-server-renderer\": \"^2.7.10\",\r\n \"vue-template-compiler\": \"^2.7.10\"\r\n },\r\n \"devDependencies\": {\r\n \"@babel/eslint-parser\": \"^7.19.1\",\r\n \"@nuxtjs/eslint-config\": \"^11.0.0\",\r\n \"@nuxtjs/eslint-module\": \"^3.1.0\",\r\n \"eslint\": \"^8.24.0\",\r\n \"eslint-plugin-nuxt\": \"^4.0.0\",\r\n \"eslint-plugin-vue\": \"^9.5.1\",\r\n \"sass\": \"^1.62.1\",\r\n \"sass-loader\": \"^10.4.1\"\r\n }\r\n```",[],74,"Unknown custom element: \u003CIcon> - did you register the component correctly?","2023-08-07T11:42:06Z","https://github.com/nuxt/icon/issues/74",0.7138648,{"description":3100,"labels":3101,"number":3105,"owner":3020,"repository":3021,"state":3039,"title":3106,"updated_at":3107,"url":3108,"score":3109},"Can't we define where we'll be storing those custom icon components in our project?\r\nThis sounds more sane `components/icons`... I looked at the source, but I found nothing that defines this path.\r\n\r\nSo could be that I'm blind, or this `global` directory is something that Nuxt handles?\r\n\r\nKind regards.",[3102],{"name":3103,"color":3104},"question","d876e3",60,"Why `components/global` exactly?","2023-03-13T14:50:53Z","https://github.com/nuxt/icon/issues/60",0.7164878,["Reactive",3111],{},["Set"],["ShallowReactive",3114],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$flp2C7W438chfDfZ21bXcNDbUChRGeH6ea3QDjChmJkg":-1},"/nuxt/icon/58"]