`\n\nUnable to use stroke-width does not take effect",[],364,"icon","Unable to use stroke-width does not take effect","2025-03-04T02:48:19Z","https://github.com/nuxt/icon/issues/364",0.744505,{"description":2023,"labels":2024,"number":2028,"owner":1994,"repository":1994,"state":1996,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### Describe the feature\n\n```ts\nconst id = ref()\nuseFetch('/api/test', {\n query: {\n id\n },\n ready: () => !!id.value\n})\n```\n\n```ts\ninterface Options {\n /** default `() => true` */\n ready: () => boolean\n // or\n // ready: MaybeRefOrGetter\u003Cboolean>\n}\n```\n\n Whenever the handler is executed, if ready is false, prevent the execution of handler.\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2025],{"name":2026,"color":2027},"pending triage","E99695",29788,"`ready` option for `useFetch` to control requests","2024-11-05T06:26:41Z","https://github.com/nuxt/nuxt/issues/29788",0.74863917,{"description":2034,"labels":2035,"number":2036,"owner":1994,"repository":2017,"state":1996,"title":2037,"updated_at":2038,"url":2039,"score":2040},"Hi there. Is there any way we could add a feature that minifies the CSS generated by this plugin and/or then extracts the code to a single separate CSS file, rather than having it all output in the ```\u003Chead>``` element?\n\nEven with...\n```javascript\nvite: {\n\tbuild: {\n\t\t\tassetsInlineLimit: 0, // default is 4096 (4 KiB); threshold to inline assets as base64 URLs\n\t\t\tcssCodeSplit: false, // if false, all CSS in the entire project will be extracted into a single CSS file\n\t}\n}\n``` \n...in my ```nuxt.config.ts``` file, the icon-related CSS code from this plugin still gets output onto my pages un-minified *and* un-extracted.\n\nThanks. :-)\n",[],327,"Don't force CSS to be inline","2024-12-22T00:14:16Z","https://github.com/nuxt/icon/issues/327",0.7505058,{"description":2042,"labels":2043,"number":2048,"owner":1994,"repository":1995,"state":1996,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.4.0, @vueuse/nuxt@10.11.1, @nuxt/ui@2.19.2, @pinia/nuxt@0.5.5, nuxt-echarts@0.2.4\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-8d9s2j?file=app.vue\n\n### Description\n\nThe UInput component does not handle compositionstart and compositionend events, resulting in issues for languages that rely on input composition, such as Chinese (e.g., Pinyin input). Vue’s default behavior for v-model on native input elements ensures that updates are delayed until the composition ends, preventing intermediate values from triggering updates. However, the UInput component currently lacks this mechanism, causing inconsistencies with Vue’s default form handling and leading to unexpected behavior during text composition.\n\n### Additional context\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003Cinput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[2044,2045],{"name":1985,"color":1986},{"name":2046,"color":2047},"triage","ffffff",2713,"UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.75067914,{"description":2054,"labels":2055,"number":2065,"owner":1994,"repository":2066,"state":2067,"title":2068,"updated_at":2069,"url":2070,"score":2071},"I'm setting up the nuxt-vitest module in my project. Though I'm running into some issues getting a simple test, I use mountSuspended(Logo) to test the mounting of a Logo component. This component uses i18n. Whereas when I'm using mount from Vitest the test passes.\r\n\r\nThe error I'm getting is as follows:\r\n```\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nSyntaxError: Need to install with `app.use` function\r\n ❯ Module.createCompileError ../node_modules/.pnpm/@intlify+message-compiler@9.3.0-beta.17/node_modules/@intlify/message-compiler/dist/message-compiler.mjs:54:19\r\n ❯ createI18nError ../node_modules/.pnpm/vue-i18n@9.3.0-beta.17_vue@3.3.4/node_modules/vue-i18n/dist/vue-i18n.runtime.mjs:97:34\r\n 96| [I18nErrorCodes.INVALID_ARGUMENT]: 'Invalid argument',\r\n 97| [I18nErrorCodes.MUST_BE_CALL_SETUP_TOP]: 'Must be called at the top of a `setup` function',\r\n 98| [I18nErrorCodes.NOT_INSLALLED]: 'Need to install with `app.use` function',\r\n | ^\r\n 99| [I18nErrorCodes.UNEXPECTED_ERROR]: 'Unexpected error',\r\n 100| [I18nErrorCodes.NOT_AVAILABLE_IN_LEGACY_MODE]: 'Not available in legacy mode',\r\n ❯ Module.useI18n ../node_modules/.pnpm/vue-i18n@9.3.0-beta.17_vue@3.3.4/node_modules/vue-i18n/dist/vue-i18n.runtime.mjs:2253:15\r\n ❯ setup app.vue:33:40\r\n```\r\n\r\nAnd while we are at it. Is there a way to test with the translated i18n messages iso the keys?\r\n\r\n######\r\n\r\nHere are some snippets from my configuration.\r\nvitest.config.js\r\n```\r\n...\r\nexport default defineVitestConfig({\r\n resolve: {\r\n alias\r\n },\r\n test: {\r\n dir: tests,\r\n setupFiles: ['tests/unit.setup.ts'],\r\n environment: 'jsdom',\r\n globals: true,\r\n root: rootDir,\r\n environmentOptions: {\r\n nuxt: {\r\n rootDir\r\n }\r\n }\r\n }\r\n})\r\n```\r\n\r\n./test/nuxt/components/Logo.nuxt.spec.ts (with mountSuspended)\r\n```\r\nimport { describe, it, expect } from 'vitest'\r\n\r\nimport { mountSuspended } from 'vitest-environment-nuxt/utils'\r\nimport Logo from '@/components/header/Logo.vue'\r\n\r\ndescribe('HeaderLogo', () => {\r\n it('can mount some component', async () => {\r\n const component = await mountSuspended(Logo)\r\n expect(component.vm).toBeTruthy()\r\n expect(component.text()).toMatchInlineSnapshot(\r\n '\"global.logo-brand-name.global.logo-brand-localehomepage.logo-tagline\"'\r\n )\r\n })\r\n})\r\n```\r\n./tests/unit.setup.ts\r\n```\r\nimport { config } from '@vue/test-utils'\r\nimport { createI18n } from 'vue-i18n'\r\n\r\nimport nlNL from '~/locales/nl_NL.json'\r\n\r\nconst i18n = createI18n({\r\n legacy: false,\r\n locale: 'nl_NL',\r\n missing: (_, key) => key,\r\n messages: {\r\n nlNL\r\n }\r\n})\r\n\r\nconfig.global.mocks = {\r\n t: msg => msg\r\n}\r\nconfig.global.plugins.push(i18n)\r\n```\r\n\r\n\r\n./tests/nuxt/components/Logo.nuxt.spec.ts (without mountSuspended)\r\n```\r\nimport { mount } from '@vue/test-utils'\r\nimport { describe, it, expect } from 'vitest'\r\n\r\nimport Logo from '@/components/header/Logo.vue'\r\n\r\ndescribe('HeaderLogo', () => {\r\n it('can mount some component', () => {\r\n const component = mount(Logo)\r\n expect(component.vm).toBeTruthy()\r\n expect(component.text()).toMatchInlineSnapshot(\r\n '\"global.logo-brand-name.global.logo-brand-localehomepage.logo-tagline\"'\r\n )\r\n })\r\n})\r\n```\r\n\r\n",[2056,2059,2062],{"name":2057,"color":2058},"vitest-environment","b60205",{"name":2060,"color":2061},"needs reproduction","DE7793",{"name":2063,"color":2064},"closed-by-bot","ededed",585,"test-utils","closed","mountSuspended with i18n","2025-01-22T12:49:12Z","https://github.com/nuxt/test-utils/issues/585",0.70203495,{"description":2073,"labels":2074,"number":2082,"owner":1994,"repository":1995,"state":2067,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2075,2076,2079],{"name":1985,"color":1986},{"name":2077,"color":2078},"documentation","0075ca",{"name":2080,"color":2081},"duplicate","cfd3d7",2429,"DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.7253371,{"description":2088,"labels":2089,"number":2092,"owner":1994,"repository":1995,"state":2067,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2090,2091],{"name":2005,"color":2006},{"name":1988,"color":1989},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.73029387,{"description":2098,"labels":2099,"number":2100,"owner":1994,"repository":2101,"state":2067,"title":2102,"updated_at":2103,"url":2104,"score":2105},"### Environment\r\n\r\n-\r\n\r\n### Reproduction\r\n\r\n\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nThe search field resizing behavior on `nuxt.com/docs` is pretty weird.\r\n1) On tablet it overlap the logo, \r\n2) Then it's collapse into a button on the right, \r\n3) Finally it change to the left\r\n\r\nAlso it's kinda annoying that the search is not available on the homepage of nuxt.com like it used to on nuxtjs.org !\r\nMaybe the search should always be an icon (like nuxtjs.org) or remove the social media from the header.\r\nAll the icon in the header could be bigger, 20x20 is too small of a tap target anyway.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[],1255,"nuxt.com","Nuxt.com search field overlap elements","2023-10-10T14:44:45Z","https://github.com/nuxt/nuxt.com/issues/1255",0.7325163,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"j0NOWpDUzB2WzE28M96rjW0lNJeWieDzfYOe6d-UMyI":-1},"/nuxt/ui/2840"]