`\n\nit doesn't work that way\n\nI really ask for help!",[2044,2045],{"name":2008,"color":2009},{"name":1988,"color":1989},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.71220636,{"description":2052,"labels":2053,"number":2057,"owner":1997,"repository":1998,"state":1999,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Description\n\nWhen adding `UButton` component with `ghost` or `link` variant inside a `UBanner` with `links` attribute, they remain displayed in black text, even if the banner has a dark background (e.g., primary color). Unlike the Banner close button, which has specific Tailwind classes that adapt it to dark mode (white text), these elements do not automatically adjust their colors.\n\n\n\n```html\n \u003CUBanner to=\"/guide-gouvernance-associative-crise\" icon=\"i-ph-books-duotone\" title=\"Guide Gouvernance Associative\" :actions=\"[{label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'ghost', size: 'md', trailingIcon: 'i-ph-arrow-right'}, {label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'link', size: 'md'}]\" close />\n```\n\nWould it be relevant to add a global attribute to components like Button, Badge, etc., to force their appearance in dark (or light) mode, regardless of the global setting? This would ensure better visual consistency when these elements are placed on a colored background (e.g., `UPageCTA` with `solid` variant).\n\n### Additional context\n\n_No response_",[2054,2055,2056],{"name":2022,"color":2023},{"name":1988,"color":1989},{"name":1994,"color":1995},3307,"Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.71548456,{"description":2063,"labels":2064,"number":2065,"owner":1997,"repository":2066,"state":1999,"title":2067,"updated_at":2068,"url":2069,"score":2070},"I've been having an issue with this module, where the fetching of font files sometimes fails during the production build. I haven't been able to create a reliable reproduction yet—it seems to happen at random.\n\nThe build is done in GitHub CI, where a Docker image is built, using Node version 18.\n\nThis is the error log from the problematic deployment:\n```\n#25 20.31 [@nuxt/fonts] ERROR Could not fetch metadata for Red Hat Display from google. fetch failed\n#25 20.31 \n#25 20.31 at Object.fetch (node:internal/deps/undici/undici:11372:11)\n#25 20.31 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n#25 20.31 at async getFontDetails$5 (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:550:12)\n#25 20.31 at async cachedData (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:474:20)\n#25 20.31 at async Object.resolveFontFaces (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:511:14)\n#25 20.31 at async resolveFontFaceWithOverride (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1395:26)\n#25 20.31 at async addFontFaceDeclaration (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:940:22)\n#25 20.31 at async Promise.all (index 0)\n#25 20.31 at async transformCSS (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1013:5)\n#25 20.31 at async Object.transform (/opt/project/node_modules/.pnpm/@nuxt+fonts@0.8.0_ioredis@5.4.1_magicast@0.3.5_rollup@4.20.0_vite@5.4.3_@types+node@22.5.5_sa_d6a46d5cxhijk7lxvuwfjdzkcm/node_modules/@nuxt/fonts/dist/module.mjs:1025:17)\n#25 20.31 \n#25 20.31 \n#25 20.31 [@nuxt/fonts] WARN Could not produce font face declaration from google for font family Red Hat Display.\n#25 20.31 \n#25 42.48 ℹ ✓ 1387 modules transformed.\n```\n\nHas anyone else come across this issue? Wouldn't it be better to exit rather than continue with the build if the font fetch fails?",[],356,"fonts","Fonts sometimes missing in production build","2024-12-05T16:49:07Z","https://github.com/nuxt/fonts/issues/356",0.7155997,{"description":2072,"labels":2073,"number":2065,"owner":1997,"repository":2074,"state":1999,"title":2075,"updated_at":2076,"url":2077,"score":2070},"We’ve consistently ran into issues with hydration and `useId` across some Nuxt projects and I think we finally found the culprit. I've forked the example from https://github.com/nuxt/icon/issues/310 and slightly altered it to reproduce the issue. Both `svg` and `css` mode lead to the error. Might it be related to the custom api endpoint?\n\n```\n[Vue warn]: Hydration attribute mismatch on \u003Cinput id=\"v-1-0\"> \n - rendered on server: id=\"v-1-0\"\n - expected on client: id=\"v-0-0\"\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\n You should fix the source of the mismatch. \n at \u003CCustomInput> \n at \u003CTestComponent> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```\n\nThe reproduction can be found here:\nhttps://stackblitz.com/edit/github-pz2kcg-jtmax8ot?file=nuxt.config.ts",[],"icon","Hydration mismatch with useId() if \u003CIcon /> is used","2025-03-24T06:38:50Z","https://github.com/nuxt/icon/issues/356",{"description":2079,"labels":2080,"number":2083,"owner":1997,"repository":2084,"state":2085,"title":2086,"updated_at":2087,"url":2088,"score":2089},"Following @Flosciante reviews here https://github.com/nuxtlabs/nuxt.com/pull/802, we need to remove listener on unMounted, we can achieve this easily with VueUse `useEventListener` which does that automatically: https://vueuse.org/core/useEventListener/#useeventlistener.",[2081],{"name":2022,"color":2082},"1ad6ff",804,"nuxt.com","closed","[Home] Replace `window.addEventListener` with `useEventListener`","2023-09-05T08:18:37Z","https://github.com/nuxt/nuxt.com/issues/804",0.6724416,{"description":2091,"labels":2092,"number":2096,"owner":1997,"repository":1997,"state":2085,"title":2097,"updated_at":2098,"url":2099,"score":2100},"I have scroll event listeners in one of the components that I am using on particular Page. The problem is this event listeners is triggered even after I navigate out of this page (where I am using this component). How to fix it? I got console full of errors. \r\n\r\n```js\r\ncreated () {\r\n if (process.browser) {\r\n window.addEventListener('scroll', this.parallax)\r\n }\r\n },\r\n destroyed () {\r\n if (process.browser) {\r\n window.removeEventListener('scroll', this.parallax)\r\n }\r\n }\r\n```\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/c1945\">#c1945\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2093],{"name":2094,"color":2095},"2.x","d4c5f9",2206,"Event listener doesn't remove when route to other page","2023-01-18T15:54:59Z","https://github.com/nuxt/nuxt/issues/2206",0.689824,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"NZIMvOVLvOsRtJ0ATrCOgyDuoAzOdIjBpgqju0JbGWY":-1},"/nuxt/nuxt.com/1370"]