// LeafIcon is icon component inside components/global\r\n`\r\n\r\nBut when I try to remove/disable suffix for the components folder for auto imports like this in my nuxt.config.ts it is not working (ie. above global icon not working ):\r\n```\r\nexport default defineNuxtConfig({\r\n components: [\r\n {\r\n path: '~/components',\r\n pathPrefix: false\r\n }\r\n ]\r\n)}\r\n```\r\n\r\nI also tried to enable prefix for components/global folder as that might be the issue causing the global icon not being imported.\r\n```\r\nexport default defineNuxtConfig({\r\n components: [\r\n {\r\n path: '~/components',\r\n pathPrefix: false\r\n },\r\n {\r\n path: '~/components/global',\r\n pathPrefix: true\r\n }\r\n ]\r\n)}\r\n```\r\n\r\nEven after doing this I was not able to solve this issue. Is there anything wrong that I have been doing or is it just the issue of nuxt? I just wanted to remove the prefix for components folder as working with larger components nested inside components folder like `components/page/search/TopBanner.vue` would make things complicated as we have to write `\u003CPageSearchTopBanner />` for auto importing that component. Please help on this as I am not able to use the components/global icons for my nuxt-icon.",[],124,"icon","Nuxt Icons unable to resolve the components/global icons when components prefix has been disabled","2024-07-29T16:08:22Z","https://github.com/nuxt/icon/issues/124",0.7142294,{"description":2050,"labels":2051,"number":2057,"owner":1991,"repository":1992,"state":2020,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Environment\n\nWhen navigating to any component on the `ui.nuxt.com` website, it displays a 500 error and fails to show any content.\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://ui.nuxt.com\n\n### Description\n\nWhen using the `ui.nuxt.com` website and navigating to any component, the site 500 errors.\n\n### Additional context\n\nOnly seems to occur on the latest version of firefox, works fine on chrome.\n\n### Logs\n\n```shell-script\n\n```",[2052,2053,2054],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2055,"color":2056},"triage","ffffff",3804,"`ui.nuxt.com` 500 errors","2025-04-08T00:51:08Z","https://github.com/nuxt/ui/issues/3804",0.7373119,{"description":2063,"labels":2064,"number":2065,"owner":1991,"repository":2044,"state":2020,"title":2066,"updated_at":2067,"url":2068,"score":2069},"After integrating `@nuxt/icon` into my project, I noticed a significant increase in the build size from approximately **2MB** to **14MB**. This issue persists even though I am not using any `\u003CIcon />` elements in my components. Additionally, I am encountering numerous deprecation warnings related to `@iconify`.\r\n\r\nIt appears that `@nuxt/icon` is downloading all icon collections instead of only the icons being used, leading to the substantial increase in build size.\r\n\r\n\r\n\r\n**Before adding `@nuxt/icon`**\r\n\r\n\r\n\r\n**After adding `@nuxt/icon`, `@iconify-json/heroicons` and `@iconify-json/tabler`**\r\n\r\n\r\n\r\nThe build size should not increase significantly, especially when no `\u003CIcon />` elements are used.\r\n\r\nIf relevant, here are the versions I am using:\r\n```\r\nNuxt Version: 3.12.3\r\n@nuxt/icon Version: ^1.0.0\r\n@iconify-json/heroicons: ^1.1.21\r\n@iconify-json/tabler: ^1.1.116\r\nNode.js Version: v20.13.1\r\n```\r\n\r\nA ton of deprecation warnings like these\r\n`\r\n(node:23176) [DEP0166] DeprecationWarning: Use of deprecated double slash resolving \".//index.cjs\" for module request \".//index.cjs\" matched to \"./*\" in the \"exports\" field module resolution of the package at ...\\node_modules\\@iconify\\vue\\package.json imported from ...\\node_modules\\nuxt-og-image\\dist\\node_modules\\_index.js.\r\n`\r\n\r\n\r\nThank you in advance for your help in fixing this issue! :)",[],188,"Significant Build Size Increase with @nuxt/icon and Deprecation Warnings from @iconify","2024-07-18T22:45:11Z","https://github.com/nuxt/icon/issues/188",0.7502299,{"description":2071,"labels":2072,"number":2074,"owner":1991,"repository":2019,"state":2020,"title":2075,"updated_at":2076,"url":2077,"score":2078},"Modules and Showcases are missing in mobile nav, presumably since migration from .md to Nuxt pages",[2073],{"name":2002,"color":2017},993,"[Code] Add missing links in mobile nav","2022-12-07T06:20:26Z","https://github.com/nuxt/nuxt.com/issues/993",0.75243676,{"description":2080,"labels":2081,"number":2084,"owner":1991,"repository":1992,"state":2020,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Description\n\nHi, I was wondering how to safelist dynamic generated tailwind classes.\n\nCurrently I hardcode an element with theses classes to generate them but I would rather prefer a safelist option somewhere. Is something like this possible?\n\nClasses that need to be compiled:\n`w-[100px] w-[140px] w-[180px] w-[220px] w-[260px] w-[300px]`\n\nCurrent solution with a hidden element:\n`\u003Cspan class=\"hidden w-[100px] w-[140px] w-[180px] w-[220px] w-[260px] w-[300px]\">\u003C/span>`",[2082,2083],{"name":1985,"color":1986},{"name":1988,"color":1989},3795,"How to safelist tailwindcss classes in nuxt 3","2025-04-04T15:19:13Z","https://github.com/nuxt/ui/issues/3795",0.7547686,{"description":2090,"labels":2091,"number":2097,"owner":1991,"repository":2035,"state":2020,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Environment\n\nWorking directory: /home/projects/github-h9agvz\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, srcDir\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-h9agvz?file=vitest.config.ts,nuxt.config.ts\n\n### Describe the bug\n\nThe coverage report (by either v8 or istanbul) does not get generated if I change the `srcDir` configuration in `nuxt.config.js`. It seems it works well if I use the default setting. You can reproduce the issue with the link I provided.\r\n\r\nIf I click on the *Coverage* icon button on `vitest-ui` web page, It shows the error text: `Cannot GET /coverage/index.html`.\r\n\r\nIf I run `vitest` with `--ui` and `coverage.enabled` option to `true` then the coverage report's `html` files should be generated in `/coverage` directory, but what I get is only `tmp` directory with `coverage.json` files included. It seems the `.html` files are not generated properly so that the output directory get empty.\r\n\r\nI even tried to change `reportsDirectory` or `root` in `vitest.config.js` but nothing changes.\n\n### Additional context\n\nSometimes if I run `vitest --ui` then after the preparation is ready, the open browser should show the Vitest UI, but it shows `Cannot GET /`. After that if I click the URL printed on the console (UI started at http://localhost:51204/__vitest__/), then it goes to the UI page. Also, if I click the *Coverage* icon on that page, it shows the error text of `Cannot GET /coverage/index.html` as well.\n\n### Logs\n\n_No response_",[2092,2093,2094],{"name":2002,"color":2003},{"name":2032,"color":2033},{"name":2095,"color":2096},"pending triage","5D08F5",869,"Coverage report does not get generated if `srcDir` in `nuxt.config.js` is modified.","2024-09-30T14:25:26Z","https://github.com/nuxt/test-utils/issues/869",0.77198356,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"U5HfXb6MWR8cAmazN4csAWyZP89MmqwlDXlfIdMynqk":-1},"/nuxt/scripts/219"]