`\r\nreturns\r\n\r\n**App.config.ts**\r\n```\r\n// https://github.com/nuxt-modules/icon#configuration-%EF%B8%8F\r\nexport default defineAppConfig({\r\n icon: {\r\n size: \"300%\", // default \u003CIcon> size applied\r\n class: \"icon\", // default \u003CIcon> class applied\r\n mode: \"css\", // svg || css\r\n aliases: {\r\n nuxt: \"logos:nuxt-icon\",\r\n },\r\n },\r\n})\r\n```\r\n",[],176,"Add universal support for color attribute (similar to CSS icons)","2024-07-15T16:06:31Z","https://github.com/nuxt/icon/issues/176",0.734228,{"description":2043,"labels":2044,"number":2047,"owner":1985,"repository":1985,"state":1987,"title":2048,"updated_at":2049,"url":2050,"score":2051},"Purgecss and @addyosmani critical shouldn't be options for Nuxt.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2438\">#c2438\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2045,2046],{"name":2014,"color":2025},{"name":2027,"color":2028},2810,"Optimization","2023-01-18T16:02:39Z","https://github.com/nuxt/nuxt/issues/2810",0.7350388,{"description":2053,"labels":2054,"number":2047,"owner":1985,"repository":2005,"state":1987,"title":2059,"updated_at":2060,"url":2061,"score":2051},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.1.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, nuxt-security@2.1.4\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://github.com/siyosu/nuxt-ui-v3\nhttps://nuxt-ui-v3.vercel.app/\n\nCourtesy @siyosu\n\n### Description\n\nHi, Nuxt-Security team here\n\nWe are investigating a bug report filed on our module here : https://github.com/nuxt-modules/security/issues/576\nWe are able to reproduce based on OP's link.\n\nWe notice that the TailwindCSS `utilities` layer is absent from the production build.\nThis is related to the fact that our module has a `{ removeLoggers: true }` default option set. If we set `{ removeLoggers: false }`, the bug disappears and the `utilities` layer is present in the production build.\n\n### Additional context\n\n**Update**.\nOur investigation has found that the root cause of this issue is because we are setting the following option in `nuxt.config.ts` \n```ts\nvite : {\n build : {\n minify: true\n }\n}\n```\n\nWe are updating the title and description of the issue to further clarify that when `vite.build.minify` is set via `defineNuxtConfig`, the Tailwind `utilities` layer will be absent from the production build.\n\n",[2055,2058],{"name":2056,"color":2057},"bug","d73a4a",{"name":2002,"color":2003},"[v3] Tailwind `utilities` layer absent in production build when vite.build.minify is used","2024-12-16T09:07:10Z","https://github.com/nuxt/ui/issues/2810",{"description":2063,"labels":2064,"number":2067,"owner":1985,"repository":2005,"state":1987,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### For what version of Nuxt UI are you asking this question?\n\nv3-alpha\n\n### Description\n\nI'm experience problems with the VS Code Tailwind Intellisense plugin. I have used ui v2 without problems so far, but when using v3 it only shows suggestions when a tailwindcss.config.ts is freshly edited, but then after reloading or restarting VS Code, it doesn't work anymore. When it's working, it only shows a few of the classes, but not the most common ones like padding, margin etc..\n\nHas someone experienced the same issue and knows a fix for that? ",[2065,2066],{"name":1999,"color":2000},{"name":2002,"color":2003},2424,"V3 Intellisense not working correctly","2024-11-05T21:44:20Z","https://github.com/nuxt/ui/issues/2424",0.73857915,{"description":2073,"labels":2074,"number":2075,"owner":1985,"repository":1986,"state":1987,"title":2076,"updated_at":2077,"url":2078,"score":2079},"\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.7411479,{"description":2081,"labels":2082,"number":2075,"owner":1985,"repository":2083,"state":1987,"title":2084,"updated_at":2085,"url":2086,"score":2079},"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",[],"scripts","Weird behaviour with lemonsqueezy script from registry","2024-07-06T11:13:23Z","https://github.com/nuxt/scripts/issues/98",["Reactive",2088],{},["Set"],["ShallowReactive",2091],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"MGOCSnClsTa7b0xwnxSJ-PhB3vaYTRRgiEW9UQWuF7Q":-1},"/nuxt/icon/84"]