\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,"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.69384795,{"description":2914,"labels":2915,"number":2931,"owner":2857,"repository":2857,"state":2872,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Environment\n\nStackblitz\r\n\r\n````\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: -\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: extends\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n````\n\n### Reproduction\n\nhttps://stackblitz.com/github/martinszeltins/found-nuxt-components-issue?file=app.vue\n\n### Describe the bug\n\nWhen I add this module to my modules array in nuxt.config.ts then I lose all typings for my components _(for both local and 3rd party components)._ It shows that components have type of `unknown`. Before I add this module, everything works.\r\n\r\n**nuxt.config.ts** 👇️\r\n```diff\r\nmodules: [\r\n+ '@nuxtjs/i18n', // This breaks all auto-import component typings (components not recognized anymore)\r\n '@vueuse/nuxt',\r\n 'nuxt-primevue'\r\n],\r\n```\r\n\r\nIf I remove it from my modules array then everything works again.\r\n\r\n**Screenshot before adding the module (everything works):** 👍️ 👇️\r\n\r\n\r\n\r\n**Screenshot after adding the module (type unknown):** ❌ 👇️\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2916,2919,2922,2925,2928],{"name":2917,"color":2918},"types","2875C3",{"name":2920,"color":2921},"3.x","29bc7f",{"name":2923,"color":2924},"workaround available","11376d",{"name":2926,"color":2927},"bug","d73a4a",{"name":2929,"color":2930},"upstream","E8A36D",26214,"Adding `@nuxtjs/i18n` to Nuxt breaks component types (shows unknown)","2024-05-27T10:28:40Z","https://github.com/nuxt/nuxt/issues/26214",0.69844824,{"description":2937,"labels":2938,"number":2943,"owner":2857,"repository":2857,"state":2872,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.5.0\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-jblieu-fynag4\n\n### Describe the bug\n\nNuxt can no longer resolve a component if its name starts with its containing folder's name, ex:\r\n\r\ncomponent path: `components/Icon/Icones`\r\n\r\napp.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CIconIcones />\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_",[2939,2940,2941],{"name":2920,"color":2921},{"name":2926,"color":2927},{"name":2942,"color":2885},"🔨 p3-minor",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.6984797,{"description":2949,"labels":2950,"number":2954,"owner":2857,"repository":2858,"state":2872,"title":2955,"updated_at":2956,"url":2957,"score":2958},"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.",[2951],{"name":2952,"color":2953},"question","d876e3",60,"Why `components/global` exactly?","2023-03-13T14:50:53Z","https://github.com/nuxt/icon/issues/60",0.69999546,{"description":2960,"labels":2961,"number":2962,"owner":2857,"repository":2858,"state":2872,"title":2963,"updated_at":2964,"url":2965,"score":2966},"\r\nHello, \r\nThanks for this wonderful module that makes it easier to use icons seamlessly in Nuxt.\r\nThere is need to fix the typo for **icon** under the _**attributes**_ section.",[],98,"Typo in readme","2023-08-17T10:45:48Z","https://github.com/nuxt/icon/issues/98",0.7008742,{"description":2968,"labels":2969,"number":2962,"owner":2857,"repository":2871,"state":2872,"title":2970,"updated_at":2971,"url":2972,"score":2966},"I am using the new nuxt/scripts module and a little confused. I want to enable the lemonsqueezy script globally, I have multiple pages where this is needed. How should I do this? the [docs](https://scripts.nuxt.com/scripts/payments/lemon-squeezy#example) tell me to do the below and I added this in my `app.vue`\r\n\r\n```html\r\n\u003Cscript setup>\r\nconst { Setup } = useScriptLemonSqueezy();\r\nonMounted(() => {\r\n Setup();\r\n});\r\n\u003C/script>\r\n```\r\n\r\nWhats happening\r\n\r\n1. `index.vue` pages opens the checkout overlay\r\n2. `[...productId].vue` pages open the checkout overlay if I open the page directly, but not when I navigate to this page from a `\u003CNuxtLink />` \r\n\r\nI thought this was an issue with the lemon.js script, but when I navigate to the product page from a NuxtLink, I can see `window.LemonSqueezy` has a been initiated which is confusing me even further, everything is working from both parties yet the checkout wont open in the overlay.\r\n\r\nHere's a repro - https://stackblitz.com/edit/github-zk9jpe?file=pages%2Findex.vue",[],"Weird behaviour with lemonsqueezy script from registry","2024-07-06T11:13:23Z","https://github.com/nuxt/scripts/issues/98",["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGSET5eeCEPRKBlJcqtxCqzY6esdp6ECC4lmoY6A-ZgA":-1},"/nuxt/icon/201"]