\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.59585977,{"description":2021,"labels":2022,"number":551,"owner":1985,"repository":1986,"state":2015,"title":2026,"updated_at":2027,"url":2028,"score":2029},"I know `\u003CIcon>` is much sexier than `\u003CNuxtIcon>` or `\u003CNIcon>` but maybe in order to avoid conflicting we can prefix component name too?",[2023],{"name":2024,"color":2025},"enhancement","a2eeef","Using two part component name","2022-09-07T13:21:28Z","https://github.com/nuxt/icon/issues/3",0.6347507,{"description":2031,"labels":2032,"number":2033,"owner":1985,"repository":1986,"state":2015,"title":2034,"updated_at":2035,"url":2036,"score":2037},"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.6981715,{"description":2039,"labels":2040,"number":2041,"owner":1985,"repository":1986,"state":2015,"title":2042,"updated_at":2043,"url":2044,"score":2045},"So in my case in nuxt.config.ts i described custom collection \r\nicon: {\r\n customCollections: [\r\n {\r\n prefix: 'elfi',\r\n dir: './assets/icons'\r\n },\r\n ],\r\n}\r\n\r\nif in my directory lies files with EN names - all works fine\r\nif i put there file with cyrillic (for ex RU) name - the nuxt even can't start properly with \"npm run dev\" - blank screen with no errors\r\n\r\nand one else thing - if i make some changes in folder with icons - i need to terminate nuxt and run again \"npm run dev\" to activate changes",[],201,"Seems like @nuxt/icon doesn't understand other language in files name in local icon collection","2024-07-16T20:38:16Z","https://github.com/nuxt/icon/issues/201",0.71156114,{"description":2047,"labels":2048,"number":2041,"owner":1985,"repository":2050,"state":2015,"title":2051,"updated_at":2052,"url":2053,"score":2045},"### 🆒 Your use case\r\n\r\nI would love to use the `ScriptGoogleMaps` component but I dont like the static placeholder. Instead I would like to immediately display the map.\r\n\r\n### 🆕 The solution you'd like\r\n\r\nAdd a prop to disable the placeholder / static map feature entirely.\r\n\r\n### ℹ️ Additional info\r\n\r\nReasons:\r\n- Static Map has a max resolution that is very low and therefor always looks blurry on high dpi screens\r\n- Static Map cant be [styled](https://snazzymaps.com/)\r\n- It takes some time until the scripts are loaded and the map is initialized. Therefor the \"activate map on hover\" doesnt work from a UX perspective",[2049],{"name":2024,"color":2025},"scripts","Google Maps: Add option to disabled placeholder","2024-09-03T15:45:42Z","https://github.com/nuxt/scripts/issues/201",{"description":2055,"labels":2056,"number":2057,"owner":1985,"repository":1986,"state":2015,"title":2058,"updated_at":2059,"url":2060,"score":2061},"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```",[],18,"Feature: Possible to change the icons directory","2023-01-19T16:59:35Z","https://github.com/nuxt/icon/issues/18",0.71322334,{"description":2063,"labels":2064,"number":2071,"owner":1985,"repository":1985,"state":2015,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### 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_",[2065,2068],{"name":2066,"color":2067},"3.x","29bc7f",{"name":2069,"color":2070},"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.7191751,["Reactive",2077],{},["Set"],["ShallowReactive",2080],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"lp2C7W438chfDfZ21bXcNDbUChRGeH6ea3QDjChmJkg":-1},"/nuxt/icon/58"]