\" },\r\n \"b\": { \"body\": \"\u003Cpath d=\\\"_path_b_\\\"/>\" },\r\n \"c\": { \"body\": \"\u003Cpath d=\\\"_path_c_\\\"/>\" }\r\n },\r\n \"width\": 24,\r\n \"height\": 24,\r\n}\r\n```\r\n\r\nExample API response to `GET /api/iconify-provider/my-icons.json?icons=a,c`\r\n```json\r\n{\r\n \"prefix\": \"my-icons\",\r\n \"icons\": {\r\n \"a\": { \"body\": \"\u003Cpath d=\\\"_path_a_\\\"/>\" },\r\n \"c\": { \"body\": \"\u003Cpath d=\\\"_path_c_\\\"/>\" }\r\n },\r\n \"width\": 24,\r\n \"height\": 24,\r\n}\r\n```\r\n\r\nModule would have to register the custom provider with iconify library:\r\n```ts\r\nimport { addAPIProvider } from '@iconify/vue'\r\naddAPIProvider('nuxt', { resources: ['/api/iconify-provider'] })\r\n```\r\n\r\nAnd the icons should be usable as per example:\r\n```html\r\n\u003Cicon name=\"@nuxt:my-icons:a\"/>\r\n\u003Cicon name=\"@nuxt:my-icons:c\"/>\r\n```",[],97,"Feature Request: Built-in API provider for custom IconifyJSON","2024-10-25T16:58:25Z","https://github.com/nuxt/icon/issues/97",0.68809193,{"description":3209,"labels":3210,"number":3218,"owner":3154,"repository":3194,"state":3195,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nHi there 👋\n\nI'm wondering if there are any plans to support UnoCSS as an alternative to Tailwind CSS in Nuxt UI 3? \n\nCurrently Nuxt UI is tightly coupled with Tailwind CSS. Given that UnoCSS is gaining popularity in the Vue ecosystem and offers great performance benefits, it would be amazing to have UnoCSS as an option.",[3211,3214,3217],{"name":3212,"color":3213},"duplicate","cfd3d7",{"name":3215,"color":3216},"question","d876e3",{"name":3188,"color":3189},2660,"Question: Any plans to support UnoCSS in Nuxt UI 3?","2024-11-16T13:24:37Z","https://github.com/nuxt/ui/issues/2660",0.69966066,{"description":3224,"labels":3225,"number":3229,"owner":3154,"repository":3154,"state":3195,"title":3230,"updated_at":3231,"url":3232,"score":3233},"I've got tailwind working with PurgeCSS with Nuxt. But I am unable to get `@apply` to work in Vue Single File Components. \r\n\r\nThe only way around this is to put everything in my `main.scss`. And the consequence of this is I lose the ability for code splitting in the SFC.\r\n\r\nAnyone got an idea how to fix this?\r\n\r\nAdding `@tailwind utilities;` does it but it adds the whole utility into server-bundle.json on `yarn build` hence bloating the built files. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1990\">#c1990\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3226],{"name":3227,"color":3228},"2.x","d4c5f9",2273,"Integrating TailwindCSS into Nuxt SFC ","2023-01-18T15:43:52Z","https://github.com/nuxt/nuxt/issues/2273",0.70135736,{"description":3235,"labels":3236,"number":3239,"owner":3154,"repository":3194,"state":3195,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Description\n\nI'm using Nuxt UI (@nuxt/ui) with Vue 3 + TypeScript, but without the Nuxt framework.\n\nI've registered all icons locally using @iconify/vue@5.x by calling addIcon(...) before the Vue app is mounted.\n\nEverything works perfectly in local development using vite (npm run dev) — icons are rendered correctly and no remote requests are made.\n\n❌ Problem in Production\nAfter running:\n\nbash\nCopy\nEdit\nvite build && vite preview\n...the app starts sending requests to the Iconify CDN like:\n\narduino\nCopy\nEdit\nhttps://api.iconify.design/lucide.json?icons=chevron-down\nThis breaks the application in offline/local-only networks (where internet access is restricted), even though:\n\nAll icons are correctly registered using addIcon(...)\n\nimport { addIcon } from '@iconify/vue'\nimport userIcon from '@/assets/icons/user.svg?raw'\n\naddIcon('lucide:user', {\n body: extractSvgBody(userIcon),\n width: 24,\n height: 24\n})\n\ngetIcon('lucide:user') and other names return full SVG objects at runtime\n\nThe final dist bundle contains the icon SVGs\n\nThe icon registration is done before createApp()\n\n\"sideEffects\": [\"src/icons/index.ts\"] is added to package.json to prevent tree-shaking\n\nI have to run the project on an internetless local network. Locally everything is working fine, but on production all icons making request to remote to get them. Please help me",[3237,3238],{"name":3215,"color":3216},{"name":3188,"color":3189},4498,"🚨 Issue: \u003CUIcon> fetches icons from remote CDN even when registered locally via addIcon in production","2025-07-11T14:07:47Z","https://github.com/nuxt/ui/issues/4498",0.70572424,{"description":3245,"labels":3246,"number":3247,"owner":3154,"repository":3155,"state":3195,"title":3248,"updated_at":3249,"url":3250,"score":3251},"I have nuxt icon setup with a SSG app. I'm using lucide and the collection is installed as a dependency. I run nuxt generate, but at runtime, I see my app is calling out to the Iconify API. Is this intentional? If so, why? If not, what do I need to do to get the icons included in the SSG bundle.",[],396,"Nuxt Icon Using Inconify API w/ SSG","2025-05-18T21:03:54Z","https://github.com/nuxt/icon/issues/396",0.7170599,{"description":3253,"labels":3254,"number":3256,"owner":3154,"repository":3154,"state":3195,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.2.9\n------------------------------\n\n### Reproduction\n\nRelated repository:\nhttps://github.com/serhii-chernenko/daisyui-issue\n\n- Correct styles with the Nuxt 3 single application: https://daisyui-issue-ui-playground.pages.dev\n- Broken styles with the latest versions and Nuxt 3 layers architecture: https://daisyui-issue.pages.dev\n- Fixed styles after downgrading packages such as `tailwindcss` and `@tailwindcss/vite` to the version `4.0.3`\n - Preview: https://preview.daisyui-issue.pages.dev\n - PR: https://github.com/serhii-chernenko/daisyui-issue/pull/1\n\n### Describe the bug\n\nIn combination of Nuxt 3 Layers architecture, DaisyUI library, and upgrading Tailwind CSS I have the issue described below.\n\nI also created the same issue to the DaisyUI and Tailwind repos:\n- https://github.com/saadeghi/daisyui/issues/3775\n- https://github.com/tailwindlabs/tailwindcss/issues/17648\n\nBut honestly, I'm not sure to which one it's really related. It'd be nice to involve Tailwind, Nuxt, Vite, and Daisy together, to find a root cause of this.\n\n## Steps to reproduce\n\n### Clone repo and install packages\n\n```\ngit clone git@github.com:serhii-chernenko/daisyui-issue.git\nbun install\n```\n\n### Verify the installed versions related to `tailwind`\n\n```bash\nbun pm ls --all | grep tailwindcss\n├── ...\n├── @tailwindcss/vite@4.1.3\n├── tailwindcss@4.1.3\n```\n\n### Run a single Nuxt 3 application\n\n```\ncd src/layers/ui\nbun run dev\n```\n\nOpen http://localhost:3000\n\nExpected result (buttons do nothing, it's just UI):\n\n\nDeployed version is available here:\nhttps://daisyui-issue-ui-playground.pages.dev\n\n### Run the end application in Nuxt 3 Layers architecture\n\n```\ncd ../../../\nbun run build:app # it's necessary to generate the `wrangler.json` file\nbun run dev:app\n```\n\nOpen http://localhost:3000\n\nExpected result (DaisyUI styles completely broken, but Tailwind's styles work as expected):\n\n\nDeployed version is available here:\nhttps://daisyui-issue.pages.dev\n\n### Downgrade `tailwindcss` and `@tailwindcss/vite` to `4.0.3`\n\nAdd to the root `package.json` file the next content:\n```json\n\"overrides\": {\n \"@tailwindcss/vite\": \"4.0.3\",\n \"tailwindcss\": \"4.0.3\"\n}\n```\n\nOr just switch to the branch:\n```bash\ngit checkout fix/downgraded-tailwind-and-tailwind-vite-versions\n```\n\nPR is available here:\nhttps://github.com/serhii-chernenko/daisyui-issue/pull/1\n\nReinstall packages:\n```\nbun install\n```\n\nVerify packages again:\n```bash\nbun pm ls --all | grep tailwindcss\n├── ...\n├── @tailwindcss/vite@4.0.3\n├── tailwindcss@4.0.3\n```\n\n### Run the end application in Nuxt 3 Layers architecture again\n\n```\nbun run build:app # it's necessary to generate the `wrangler.json` file\nbun run dev:app\n```\n\n### Additional context\n\nI had the same issue with Node v20. There's no difference in the package manager.\n\n### Logs\n\n```shell-script\n\n```",[3255],{"name":3174,"color":3175},31773,"Latest `tailwindcss` and `@tailwindcss/vite` packages don't compile DaisyUI styles in Nuxt 3 Layers architecture","2025-04-11T20:20:35Z","https://github.com/nuxt/nuxt/issues/31773",0.72119355,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqAcJ7vZrbrTWI2t-5bWlvnVHm5xZD8_tvDNiqN6gUiA":-1},"/nuxt/nuxt.com/57"]