","2024-06-14T16:02:02Z","https://github.com/nuxt/nuxt/issues/10412",0.7610494,{"description":3086,"labels":3087,"number":3095,"owner":3028,"repository":3029,"state":3070,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Environment\n\n- Node version: `22.13`\n- Nuxt version: `3.15`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.11\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/affectionate-sky-8vxn4g\n\n### Description\n\nWhen using `compatibilityVersion: 4`, the `dir` in `icon.customCollections` should be absolute path (`./app/assets/icons`):\n```\n✔ Nuxt Icon loaded local collection custom with 1 icons\n```\n\nOtherwise, when using `~/assets/icons`, it doesn't find any icon:\n```\n✔ Nuxt Icon loaded local collection custom with 0 icons\n```\n\n\n\n### Additional context\n\nnuxt.config.ts\n```js\nexport default defineNuxtConfig({\n modules: [\"@nuxt/ui\"],\n devtools: { enabled: true },\n compatibilityDate: \"2024-12-19\",\n future: {\n compatibilityVersion: 4,\n },\n icon: {\n customCollections: [\n {\n prefix: \"custom\",\n dir: \"~/assets/icons\", // not working\n // dir: \"./app/assets/icons\", // it works\n },\n ],\n },\n});\n```\n\n### Logs\n\n```shell-script\n\n```",[3088,3091,3092],{"name":3089,"color":3090},"bug","d73a4a",{"name":3022,"color":3023},{"name":3093,"color":3094},"upstream","78bddb",3133,"Custom icon collection path bug when using Nuxt v4 directory structure","2025-03-26T15:17:29Z","https://github.com/nuxt/ui/issues/3133",0.7777951,{"description":3101,"labels":3102,"number":3104,"owner":3028,"repository":3029,"state":3070,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.15.1\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.13.2\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.9\r\n- Builder: -\r\n- User Config: app, colorMode, compatibilityDate, css, devServer, devtools, i18n, modules, openFetch, runtimeConfig, ssr, tailwindcss\r\n- Runtime Modules: @nuxt/ui@2.18.0, @pinia/nuxt@0.5.1, nuxt-icons@3.2.1, @nuxtjs/i18n@8.5.3, nuxt-open-fetch@0.9.1\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\nv.2.18.0\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-k1f28x?file=app.config.ts\r\n\r\n### Description\r\n\r\nSince updating the library to version 2.18.0, custom variants defined in the app.config.ts are no longer recognized by TypeScript, resulting in type errors when using these custom variants in the code.\r\n\r\nSteps to reproduce:\r\n\r\n1. Define a custom variant in app.config.ts\r\n2. Observe TypeScript type errors indicating the variant is not recognized when using it to custom another button ( in app.config.ts )\r\n\r\nExpected behavior: Custom variants should be properly recognized and validated by TypeScript, as they were in versions prior to 2.18.0.\r\n\r\nThank you for your help in resolving this issue!\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3103],{"name":3089,"color":3090},2221,"Custom variants not recognized by TypeScript in app.config.ts after updating to v2.18.0","2024-11-26T13:14:03Z","https://github.com/nuxt/ui/issues/2221",0.7794301,{"labels":3110,"number":3124,"owner":3028,"repository":3028,"state":3070,"title":3125,"updated_at":3126,"url":3127,"score":3128},[3111,3112,3115,3118,3121],{"name":3019,"color":3078},{"name":3113,"color":3114},"good first issue","fbca04",{"name":3116,"color":3117},"types","2875C3",{"name":3119,"color":3120},"3.x","29bc7f",{"name":3122,"color":3123},"dx","C39D69",15148,"Autocompletion for the `target` attribute of the `\u003CNuxtLink>` component","2023-01-19T17:45:16Z","https://github.com/nuxt/nuxt/issues/15148",0.7808185,{"description":3130,"labels":3131,"number":3133,"owner":3028,"repository":3028,"state":3070,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Describe the feature\r\n\r\nHello,\r\n\r\nWhen using a NuxtLink, if the href start with a protocol, 'noreferrer noopener' is automatically. While this is great in many case, when you start creating websites links between them, like documentations, you need to know if user come from one of your website.\r\n\r\nTo do so, the 'noreferrer' need to be removed. While this is possible to pass manually 'noopener' to NuxtLink, it become more complicated when there is new website, many links or even with Nuxt Content.\r\n\r\nTo solve this, I'm thinking of a white list of URL where only the 'noopener' is set, coming from a key in the Nuxt config file. \r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3132],{"name":3039,"color":3040},25466,"Allow white-list domain for NuxtLink","2025-06-06T19:54:48Z","https://github.com/nuxt/nuxt/issues/25466",0.78464824,{"description":3139,"labels":3140,"number":3142,"owner":3028,"repository":3028,"state":3070,"title":3143,"updated_at":3144,"url":3145,"score":3146},"\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7766\">#c7766\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3141],{"name":3067,"color":3068},3907,"(index.vue), How to configure dynamic parameters for root routing","2023-01-18T16:26:44Z","https://github.com/nuxt/nuxt/issues/3907",0.7849884,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRvPa2zMQq-nvphyRsKRg7X3lSK2RioPydtQNIukmYdY":-1},"/nuxt/ui/3089"]