&\r\n InjectionType\u003Ctypeof import(\"../../node_modules/.pnpm/nuxt@3.12.4_@parcel+watcher@2.4.1_@types+node@20.14.11_ioredis@5.4.1_magicast@0.3.4_rollup@4._lljhbfrgkudpe6zumtjkp3yzvi/node_modules/nuxt/dist/app/plugins/dev-server-logs\").default> &\r\n InjectionType\u003Ctypeof import(\"../../node_modules/.pnpm/nuxt@3.12.4_@parcel+watcher@2.4.1_@types+node@20.14.11_ioredis@5.4.1_magicast@0.3.4_rollup@4._lljhbfrgkudpe6zumtjkp3yzvi/node_modules/nuxt/dist/app/plugins/check-if-layout-used\").default> &\r\n InjectionType\u003Ctypeof import(\"../../plugins/test\").default>\r\n```\r\n\r\nThe file `node_modules/@nuxt/icon/dist/runtime/plugin.d.ts` is empty.\r\n\r\nReproduction:\r\nhttps://stackblitz.com/edit/github-upzndu?file=plugins%2Ftest.ts,app.vue (stackblitz's types don't work in .vue files, test it in local)",[2967,2969],{"name":2942,"color":2968},"d73a4a",{"name":2970,"color":2971},"upstream","B4199A",214,"nuxt/icon breaks nuxt's plugin system types","2024-07-23T14:03:19Z","https://github.com/nuxt/icon/issues/214",0.7037205,{"description":2978,"labels":2979,"number":2981,"owner":2905,"repository":2982,"state":2945,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: modules\r\n- Runtime Modules: @nuxt/ui@2.18.3\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\n2.18.1\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-snm3l2?file=app.config.ts\r\n\r\n### Description\r\n\r\nIf using {color} in app.config.ts variants (https://ui.nuxt.com/getting-started/theming#smart-safelisting), even with \"primary\", the generated classes are ignored by tailwind. See reproduction (hover classes)\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2980],{"name":2942,"color":2968},2007,"ui","Issue with using {color} in app.config.ts variants","2025-03-28T17:31:38Z","https://github.com/nuxt/ui/issues/2007",0.7049923,{"description":2988,"labels":2989,"number":2996,"owner":2905,"repository":2982,"state":2945,"title":2997,"updated_at":2998,"url":2999,"score":3000},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\n### Environment\n\n* Operating System: Linux\n* Node Version: v20.15.1\n* Nuxt Version: 3.14.1592\n* Package Manager: npm@10.7.0\n* Nuxt UI: v3.0.0-alpha.x\n\n### Description\nHello, I have the following configurations; \n\n#### assets/css/main.css\n```css\n@import \"tailwindcss\";\n@import \"@nuxt/ui\";\n\n@theme {\n /* Font Family Extend */\n --font-display: 'Work Sans', sans-serif;\n --font-content: 'Roboto', sans-serif;\n --font-condensed: 'Roboto Condensed', sans-serif;\n\n\n /* Color Extend */\n --color-brand-50: #fef4ee;\n --color-brand-100: #fcdbc5;\n --color-brand-200: #facaae;\n --color-brand-300: #f6a57b;\n --color-brand-400: #f27545;\n --color-brand-500: #ee5221;\n --color-brand-600: #df3917;\n --color-brand-700: #b92915;\n --color-brand-800: #932219;\n --color-brand-900: #772017;\n --color-brand-950: #400d0a;\n}\n\n:root {\n --ui-primary: var(--color-brand-500);\n}\n```\n\nand my nuxt.config.ts file; \n```ts\nexport default defineNuxtConfig({\n // ....\n modules: ['@nuxt/ui', '@pinia/nuxt'],\n css: ['~/assets/css/main.css', '~/assets/scss/common.scss'],\n vite: {\n css: {\n preprocessorOptions: {\n scss: { api: 'modern-compiler' }\n }\n }\n },\n // ....\n});\n```\nWith the configurations defined as above when i set ssr:false in my nuxt.config.ts, my custom color called 'brand' is not applied to components and the default green is used from the tailwind. With ssr: true everything is ok with `npm run dev`. I also tried to set the color 'brand' in app.config.ts \n\n```ts\nexport default defineAppConfig({\n ui:{\n colors: {\n primary: 'brand'\n }\n }\n});\n``` \nwith this setting again everything works but this time ts complains about `Type '\"brand\"' is not assignable to type 'Color | undefined'.ts(2322)`. \n\nI did not find a true way to set colors from extended tailwindcss color palette. Thanks in advance for any help.\n\n\nThe following screenshot; ssr: false and primary color defined on ```:root {}``` \n\n\n\nThe following screenshot; ssr: true and primary color defined on ```:root {}``` \n\n\n\n\n \nThe following screenshot; ssr: false and primary color defined on 'appconfig' but this time I have the following error from ts\n\n\n\n\n\n\nEdit 1: \n> [!IMPORTANT]\n> I also tried to extend on a types/colors.d.ts file the `tailwindcss/colors` namespace to add my custom color but no chance\n\n```ts\nimport colors from 'tailwindcss/colors'\n\n\ndeclare module 'tailwindcss/colors' {\n const colors = colors | 'brand'\n export default colors;\n}\n```\n\n",[2990,2993],{"name":2991,"color":2992},"question","d876e3",{"name":2994,"color":2995},"v3","49DCB8",2869,"Use a custom color instead of the predefined Tailwind colors with ssr false","2024-12-16T09:47:16Z","https://github.com/nuxt/ui/issues/2869",0.70812476,{"description":3002,"labels":3003,"number":3007,"owner":2905,"repository":2933,"state":2945,"title":3008,"updated_at":3009,"url":3010,"score":3011},"I'm trying to end-to-end test a middleware that redirects a user if it doesn't provide a valid auth token.\r\n\r\nBefore `nuxt-vitest` I was using `@nuxt/text-utils` to fetch a route from the test app, that the middleware was applied to.\r\n\r\nBut those two dependencies don't seem compatible with each other.\r\n\r\nHence I tried a lot of approaches but wasn't successful yet in fetching from the `nuxt-vitest` nuxt instance. I guess that might be because that instance doesn't load any routes/pages. Could this be the case?\r\n\r\nWould it make more sense to get `@nuxt/test-utils` working alongside `nuxt-vitest`, or is there a way I could migrate my previous test to `nuxt-vitest`? Would be willing to provide a PR for `nuxt-vitest` if that makes sense, but I'm not quite sure if that's something that this module tries to solve.\r\n\r\nMy current workaround is to simply unit-test the middleware by importing it.",[3004],{"name":3005,"color":3006},"vitest-environment","b60205",583,"End-to-End Test Middleware (Fetch from Nuxt Instance)","2023-12-02T00:37:12Z","https://github.com/nuxt/test-utils/issues/583",0.71091586,["Reactive",3013],{},["Set"],["ShallowReactive",3016],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwN7LFbjTAS8rZMHA-tBDHUKDO1JZZIJ1MRTQH5zyTzU":-1},"/nuxt/icon/160"]