\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```",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"triage","ffffff",2713,"nuxt","ui","open","UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.74759656,{"description":2882,"labels":2883,"number":2890,"owner":2874,"repository":2874,"state":2876,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Describe the feature\r\n\r\nNow that I think I understand composables better, especially useFetch, I see myself using it everytime I communicate to my api. Even when posting a form, because I like the out of the box reactive properties it provides.\r\n\r\nAnd now that Nuxt 3.11 adds `clear()` I feel its complete.\r\n\r\nI often end up doing this:\r\n\r\n```js\r\nconst formData = reactive({\r\n firstName: 'Peter',\r\n lastName: 'Griffin',\r\n ...\r\n});\r\n\r\nconst { status, execute: submit, clear, error } = useFetch('...', {\r\n watch: false,\r\n immediate: false,\r\n \r\n body: formData,\r\n method: 'POST',\r\n});\r\n\r\nonBeforeMount(clear); // maybe theres an even better way to automatically clear things up?\r\n```\r\n\r\nI propose to add a new composable, analog to `useLazyFetch`.\r\n\r\nIt could be named `useManualFetch`, `usePostFetch` (`usePost`?) or `useSubmitFetch` (`useSubmit`?)\r\n\r\nAnd it could be used like this:\r\n\r\n```\r\nconst formData = reactive({ ... });\r\nconst { status, error, execute: submit } = useSubmit('...', formData);\r\n```\r\n\r\nMaybe `lazy: true` and `server: false` is also a good default here? I'm not at all familiar enough with SSR and nitro at this point–\r\n\r\nI know I could make (and have made) that composable myself, but I think this is a good thing to offer out of the box to everybody.\r\n\r\nWhat do you think?\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [x] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2884,2887],{"name":2885,"color":2886},"enhancement","8DEF37",{"name":2888,"color":2889},"discussion","538de2",26306,"adding useManualFetch / usePostFetch / useSubmitFetch composable","2024-06-30T11:05:09Z","https://github.com/nuxt/nuxt/issues/26306",0.7599805,{"description":2896,"labels":2897,"number":2899,"owner":2874,"repository":2900,"state":2901,"title":2902,"updated_at":2903,"url":2904,"score":2905},"I've upgraded `@nuxt/fonts` to `v0.10.0` and after running `npm run dev` receiving the following errors:\n\n```\n[10:08:40 PM] ERROR Could not resolve font face for Segoe UI from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n[10:08:40 PM] ERROR Could not resolve font face for SFMono-Regular from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n[10:08:40 PM] ERROR Could not resolve font face for Inter from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n```\n\nI've tried to set `adobe: false` in the config, but still getting these errors. I'm using `Inter` font only: `font-family: \"Inter\", sans-serif;`\n\n\n",[2898],{"name":2868,"color":2869},328,"fonts","closed","CLI error after upgrading to v0.10.0","2024-10-08T21:31:44Z","https://github.com/nuxt/fonts/issues/328",0.7379966,{"description":2907,"labels":2908,"number":2899,"owner":2874,"repository":2909,"state":2901,"title":2910,"updated_at":2911,"url":2912,"score":2905},"I encountered an error when running npm run build in my Nuxt 3 project. The error message states:\n\n**ERROR Nuxt module should be a function: nuxt-icon**\n\nThis issue happens while trying to build the project, even after installing the latest version of nuxt-icon. The versions of the dependencies in my project are as follows:\n\n**Nuxt Version: 3.14.159\nNode Version: v18.20.4\nnuxt-icon Version: ^0.5.0\nCLI Version: 3.15.0\nNitro Version: 2.10.4**\n\nI have tried reinstalling the nuxt-icon module and performing a cleanup using npx nuxi cleanup, but the issue persists.\n\nSteps to reproduce:\n\nSet up a Nuxt 3 project.\nInstall nuxt-icon (version ^0.5.0).\nRun npm run build.\n\nThe error occurs.\nExpected behavior: The build process should complete successfully without any errors related to the nuxt-icon module.\n\nAdditional context:\n\nI am using yarn as the package manager.\nI have also checked that my nuxt.config.ts is properly configured to use nuxt-icon.\nHow to resolve:\n\nI have tried solutions such as cleaning up the cache and reinstalling dependencies, but the issue persists.\nThe issue seems to be related to the nuxt-icon module not being recognized as a function by Nuxt.\n\n\n",[],"icon","Nuxt module should be a function: nuxt-icon","2024-12-22T11:07:06Z","https://github.com/nuxt/icon/issues/328",{"description":2914,"labels":2915,"number":2922,"owner":2874,"repository":2875,"state":2901,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Description\n\nI can see there was some changes [here](https://github.com/nuxt/ui/pull/3123) which is great.\n\nI'm just wondering why the 'help' property was excluded from these additions?\n\nThank you!",[2916,2919],{"name":2917,"color":2918},"question","d876e3",{"name":2920,"color":2921},"v3","49DCB8",3685,"Was UFormField 'help' property excluded from the aria-describedby update for any specific reason?","2025-03-26T12:47:39Z","https://github.com/nuxt/ui/issues/3685",0.73945636,{"description":2928,"labels":2929,"number":2932,"owner":2874,"repository":2933,"state":2901,"title":2934,"updated_at":2935,"url":2936,"score":2937},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2930],{"name":2868,"color":2931},"ff281a",496,"nuxt.com","[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.74524754,{"description":2939,"labels":2940,"number":2932,"owner":2874,"repository":2944,"state":2901,"title":2945,"updated_at":2946,"url":2947,"score":2937},"",[2941],{"name":2942,"color":2943},"vitest-environment","b60205","test-utils","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",{"description":2949,"labels":2950,"number":2954,"owner":2874,"repository":2874,"state":2901,"title":2955,"updated_at":2956,"url":2957,"score":2958},"Thanks for producing such a popular tool. After looking over the README I noticed Node may be required to run this server-side. If a pure browser engine is running on the server is it possible to leverage this tool to take advantage of ESM? I realize there many not be a simple answer to this question. But maybe there is, and that's why I ask.\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/c1148\">#c1148\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2951],{"name":2952,"color":2953},"2.x","d4c5f9",1293,"Support for ES2015 Modules","2023-01-18T15:41:01Z","https://github.com/nuxt/nuxt/issues/1293",0.74685085,{"labels":2960,"number":2966,"owner":2874,"repository":2874,"state":2901,"title":2967,"updated_at":2968,"url":2969,"score":2970},[2961,2962,2963],{"name":2885,"color":2886},{"name":2888,"color":2889},{"name":2964,"color":2965},"3.x","29bc7f",12834,"Allow optional build-time type checking","2023-01-19T16:36:14Z","https://github.com/nuxt/nuxt/issues/12834",0.74970275,{"description":2972,"labels":2973,"number":2974,"owner":2874,"repository":2909,"state":2901,"title":2975,"updated_at":2976,"url":2977,"score":2978},"I'm using @nuxt/icon as part of @nuxt/ui, but I don't think, this makes a difference.\n\nWhat I'm doing/I'd like to do:\n- I reference the icon `mdi:cog`. It's displayed nicely in the current text color, switching light/dark mode.\n- I take the SVG code that is used in the rendered HTML. (I want to slightly modify it, but I'm not doing it just to demonstrate the issue.) I put the SVG coder into a `cog.svg` in my custom icons folder.\n- I reference it with `custom:cog`.\n\nWhat I'm expecting:\n- Both icons should behave exactly the same with respect to size/color/...\n\nWhat actually happens:\n- While the `mdi:cog` icon has text color and switches when changing dark/light mode, the `custom:cog` icon is always displayed in black.\n\nWhen looking at the rendered HTML/CSS it looks very different for custom icon than for the non-custom icon:\nWhile the `mdi:cog` uses the css propery `mask-image`, the `custom:cog` uses `background-image´.\n\nIt would be very cool to either change this behavior so that custom icons behave like regular icons or at least document the difference.",[],324,"Custom icon gets rendered differently (mask-image vs. background-image)","2024-12-18T09:49:35Z","https://github.com/nuxt/icon/issues/324",0.75059634,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fnMBEw_lpEMl3WPrUwhNWgau6v-aU_PUbRKvYTeEZghE":-1},"/nuxt/test-utils/667"]