\r\n\u003C/template>\r\n``` \r\n\r\nBy the way, [the doc state](https://ui.nuxt.com/getting-started/theming#ui-prop) that \"Each component has a ui prop\". Which is not true then.\n\n### Additional context\n\n_No response_",[2905,2908],{"name":2906,"color":2907},"enhancement","a2eeef",{"name":2872,"color":2873},2094,"Some component doesn't have a UI prop","2025-03-17T14:27:40Z","https://github.com/nuxt/ui/issues/2094",0.71552235,{"description":2915,"labels":2916,"number":2919,"owner":2875,"repository":2876,"state":2897,"title":2920,"updated_at":2921,"url":2922,"score":2923},"Todo after #2298 is merged",[2917,2918],{"name":2906,"color":2907},{"name":2869,"color":2870},2314,"Handle dynamic `--radius` token","2024-10-09T12:28:47Z","https://github.com/nuxt/ui/issues/2314",0.7173009,{"description":2925,"labels":2926,"number":2928,"owner":2875,"repository":2876,"state":2897,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### For what version of Nuxt UI are you suggesting this?\n\nv2.17.0\n\n### Description\n\nI want to set styles for other elements based on the activation state of the `ULink` component, but it was unexpectedly difficult. First, I didn't find relevant content in the [documentation](https://ui.nuxt.com/components/link) of the `ULink` component. It wasn't until I found this [issue](https://github.com/nuxt/ui/issues/1718) that I learned that I could get the activation state through `v-slot={isActive}`. Secondly, I can't directly set the `data-*` attribute for the `ULink` component to save the value of isActive, because this will prompt a ts error and the rendered `a` tag will not contain attributes, so I have to add another HTML tag as a child element of the `ULink` component to indirectly add the `data-*` attribute. \n\n### Additional context\n\n_No response_",[2927],{"name":2906,"color":2907},2726,"Use `data-*` to add activation state to `ULink`","2024-12-05T13:48:55Z","https://github.com/nuxt/ui/issues/2726",0.7237217,{"description":2934,"labels":2935,"number":2937,"owner":2875,"repository":2876,"state":2897,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.17.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.10.0\n- Builder: -\n- User Config: compatibilityDate, devServer, devtools, modules, tailwindcss, i18n, css, runtimeConfig, experimental, colorMode\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.2, @nuxtjs/i18n@9.1.1, @pinia/nuxt@0.9.0, @nuxt/ui@2.20.0, @nuxtjs/color-mode@3.5.2\n- Build Modules: -\n\n\n### Version\n\nv2.20.0\n\n### Reproduction\n\n```\n{\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\"\n },\n \"dependencies\": {\n \"@ckpack/vue-color\": \"^1.6.0\",\n \"@devui-design/icons\": \"^1.4.0\",\n \"@headlessui/vue\": \"^1.7.23\",\n \"@heroicons/vue\": \"^2.2.0\",\n \"@nuxt/icon\": \"^1.10.3\",\n \"@nuxtjs/color-mode\": \"^3.5.2\",\n \"@tailwindcss/typography\": \"^0.5.16\",\n \"@webzlodimir/vue-avatar\": \"^0.0.8\",\n \"axios\": \"^1.7.9\",\n \"devui-theme\": \"^0.0.7\",\n \"highlight.js\": \"^11.11.1\",\n \"markdown-it\": \"^14.1.0\",\n \"nuxt\": \"^3.15.0\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"devDependencies\": {\n \"@nuxt/ui\": \"2.20.0\",\n \"@nuxtjs/i18n\": \"9.1.1\",\n \"@pinia/nuxt\": \"0.9.0\",\n \"nuxt\": \"^3.15.0\",\n \"pinia\": \"^2.3.0\"\n },\n \"packageManager\": \"pnpm@9.15.2+sha512.93e57b0126f0df74ce6bff29680394c0ba54ec47246b9cf321f0121d8d9bb03f750a705f24edc3c1180853afd7c2c3b94196d0a3d53d3e069d9e2793ef11f321\"\n}\n```\n\n# tailwind.config.js\n\n```\n/** @type {import('tailwindcss').Config} */\nmodule.exports = {\n theme: {\n },\n plugins: [\n // https://stackoverflow.com/questions/75706164/problem-with-tailwind-css-when-using-the-react-markdown-component\n // 避免 tailwind 与 markdown 冲突\n require('@tailwindcss/typography'),\n ],\n}\n```\n\n# nuxt.config.ts \n```\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n compatibilityDate: '2024-11-01',\n devServer: {\n port: 4432\n },\n devtools: { enabled: true },\n modules: ['@nuxtjs/tailwindcss', '@nuxtjs/i18n', '@pinia/nuxt', '@nuxt/ui', '@nuxtjs/color-mode'],\n tailwindcss: {\n exposeConfig: true,\n viewer: true,\n },\n i18n: {\n vueI18n: './i18n.config.ts' // if you are using custom path, default\n },\n css: [\n '~/assets/main.css'\n ],\n runtimeConfig: {\n public: {\n apiBaseUrl: 'http://localhost:9384'\n },\n },\n // https://github.com/nuxt/nuxt/issues/30461\n experimental: { appManifest: false },\n colorMode: {\n preference: 'light'\n }\n})\n```\n\n# ~/assets/main.css\nempty\n\n### Description\n\n# Style loss:\n```\n \u003CUAccordion\n multiple\n :items=\"[{ label: 'What is Nuxt UI?', content: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit' }, { label: 'Getting Started', content: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit' }, { label: 'Theming', content: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit' }, { label: 'Components', content: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit' }]\"\n />\n````\nview:\n\n\n\n# process\nI installed Tailwind first, and then I installed Nuxt UI.\n\n# package.json\n\n### Additional context\n\nI installed Tailwind first, and then I installed Nuxt UI.\n\n### Logs\n\n```shell-script\n\n```",[2936],{"name":2866,"color":2867},3085,"Style loss","2025-01-14T11:03:42Z","https://github.com/nuxt/ui/issues/3085",0.7245357,{"description":2943,"labels":2944,"number":2947,"owner":2875,"repository":2948,"state":2897,"title":2949,"updated_at":2950,"url":2951,"score":2952},"http://localhost:3000/integrations?version=2.x\n\n",[2945],{"name":2866,"color":2946},"ff281a",549,"nuxt.com","[Integrations] Version selector is not valid on refresh with query param","2023-02-15T12:32:31Z","https://github.com/nuxt/nuxt.com/issues/549",0.72460276,{"description":2954,"labels":2955,"number":2947,"owner":2875,"repository":2962,"state":2897,"title":2963,"updated_at":2964,"url":2965,"score":2952},"My dev dependencies: \r\n```\r\n{\r\n \"@nuxt/devtools\": \"^0.5.5\",\r\n \"@nuxtjs/tailwindcss\": \"^6.4.1\",\r\n \"@vitest/coverage-c8\": \"^0.31.3\",\r\n \"nuxt\": \"^3.5.2\",\r\n \"nuxt-vitest\": \"0.8.2\",\r\n \"tailwindcss\": \"^3.3.2\",\r\n \"vitest\": \"^0.31.3\"\r\n }\r\n```\r\n\r\nThe app is building fine, but trying to start Vitest is causing the following error:\r\n`ERROR Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'`\r\n\r\nIt seems to be breaking down on `const { startVitest } = await import(await resolvePath(\"vitest/node\"));` in `module.mjs`\r\n\r\nIs anyone else experiencing this issue with the latest version of Nuxt or is it just me?",[2956,2959],{"name":2957,"color":2958},"vitest-environment","b60205",{"name":2960,"color":2961},"windows","6FA283","test-utils","Dynamic module import seems to be causing error","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/549",{"description":2967,"labels":2968,"number":2970,"owner":2875,"repository":2971,"state":2897,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.17.1`\r\n- Nuxt Version: `3.11.2`\r\n- CLI Version: `3.11.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `pnpm@8.6.11`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`, `hub`, `nitro`\r\n- Runtime Modules: `@nuxthub/core@0.5.16`, `@nuxt/eslint@0.3.10`, `nuxt-icon@0.6.10`, `@nuxtjs/tailwindcss@6.12.0`, `@nuxt/fonts@0.7.0`\r\n- Build Modules: `-`\r\n\r\n### Version\r\n\r\nv0.7.0\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/~/github.com/larrasu/frontend-mentor\r\n\r\n```sh\r\ncd solutions/invoice-app\r\npnpm dev\r\n```\r\n\r\n### Description\r\n\r\nI've been experiencing this error in various projects. I'm not sure why I can't reproduce the error on Stackblitz. It's the same repo and branch. The error is still showing up on my end as of now. The only way to get rid of this error is by removing `@nuxt/fonts` from the `nuxt.config.ts`. So I figured there is a conflict between`@nuxt/fonts` and `@nuxt/devtools`?\r\n\r\n### Logs\r\n\r\n```sh\r\n ERROR Cannot start nuxt: Failed to get devtools context. 12:09:04 AM\r\n\r\n at extendServerRpc (node_modules/.pnpm/@nuxt+devtools-kit@1.2.0_nuxt@3.11.2_vite@5.2.11/node_modules/@nuxt/devtools-kit/dist/index.mjs:96:11)\r\n at node_modules/.pnpm/@nuxt+fonts@0.7.0_nuxt@3.11.2_vite@5.2.11/node_modules/@nuxt/fonts/dist/module.mjs:1137:11\r\n at node_modules/.pnpm/hookable@5.5.3/node_modules/hookable/dist/index.mjs:48:66\r\n at Object.run (node_modules/.pnpm/hookable@5.5.3/node_modules/hookable/dist/index.mjs:41:43)\r\n at node_modules/.pnpm/hookable@5.5.3/node_modules/hookable/dist/index.mjs:48:56\r\n at async enableModule (/Users/larrasu/.nvm/versions/node/v16.15.1/lib/node_modules/@nuxt/devtools/dist/chunks/module-main.mjs:8466:3)\r\n at async normalizedModule (/Users/larrasu/.nvm/versions/node/v16.15.1/lib/node_modules/@nuxt/devtools/node_modules/@nuxt/kit/dist/index.mjs:169:17)\r\n at async installModule (node_modules/.pnpm/@nuxt+kit@3.11.2/node_modules/@nuxt/kit/dist/index.mjs:2415:95)\r\n at async initNuxt (node_modules/.pnpm/nuxt@3.11.2_@opentelemetry+api@1.8.0_@unocss+reset@0.59.4_drizzle-orm@0.30.10_eslint@9.2.0_fl_br3acc34oknouixgtiqiyrhd6y/node_modules/nuxt/dist/index.mjs:4233:7)\r\n at async NuxtDevServer._load (node_modules/.pnpm/nuxi@3.11.1/node_modules/nuxi/dist/chunks/dev2.mjs:6879:5)\r\n```",[2969],{"name":2866,"color":2867},149,"fonts","Cannot start nuxt: Failed to get devtools context.","2024-09-23T12:12:54Z","https://github.com/nuxt/fonts/issues/149",0.73150873,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5AF_PZiNIthAz6gQqq1ivDu43rfya-9pecUWVYROopA":-1},"/nuxt/ui/1778"]