\r\n \u003Cbutton class=\"btn btn-primary\" @click=\"sendIt\">Send\u003C/button>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nconst body = reactive({\r\n foo: 'bar',\r\n name: '',\r\n});\r\n\r\nconst sendIt = async () => {\r\n const { data, error } = await useFetch('https://httpbin.org/anything', {\r\n method: 'POST',\r\n body,\r\n });\r\n};\r\n\u003C/script>\r\n```\n\n### Describe the bug\n\nWhen POSTing a reactive Vue object using `useFetch`, I find that further modification of the object's properties causes the `useFetch` call to unexpectedly fire again for each modification.\r\n\r\nIn the above example, I have a reactive object named `body`, and I use `useFetch` to POST it somewhere. Afterward, if I modify the object using an `\u003Cinput>` with `v-model` binding, that `useFetch` POST fires again for each keypress. If I click Send to trigger `useFetch` once more, then modify the object's properties yet again, the `useFetch` calls invoked by those modifications have doubled up, and they continue to double with each click of the Send button.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3207,3208],{"name":3163,"color":3164},{"name":3149,"color":3150},23837,"useFetch calls repeat when sending and modifying reactive objects","2023-10-20T21:12:43Z","https://github.com/nuxt/nuxt/issues/23837",0.7513614,{"description":3215,"labels":3216,"number":3231,"owner":3138,"repository":3138,"state":3167,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Describe the feature\n\nCurrently, we send back all states (`useState`) from island within the island response.\r\n\r\nIt currently doesn't have any impact on the app calling the island.\r\n\r\nThere's 2 solutions:\r\n- we keep it and fix the bug where the state isn't applied to the current App\r\n - ⚠️What would happen if we have 2 island located in the same component ? Both are making a promise so the user cannot know what will happen (in which order useState will be set)\r\n- we completly remove it and reduce the json payload for island responses.\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).",[3217,3220,3221,3222,3225,3228],{"name":3218,"color":3219},"good first issue","fbca04",{"name":3163,"color":3164},{"name":3176,"color":3177},{"name":3223,"color":3224},"🔨 p3-minor","FBCA04",{"name":3226,"color":3227},"performance","E84B77",{"name":3229,"color":3230},"server components","839413",26579,"Remove or fix `state` from islands components","2024-04-20T01:56:58Z","https://github.com/nuxt/nuxt/issues/26579",0.7522963,{"description":3237,"labels":3238,"number":3239,"owner":3138,"repository":3240,"state":3167,"title":3241,"updated_at":3242,"url":3243,"score":3144},"https://github.com/nuxt-community/module-test-utils/blob/7ca4bf14e6596e9b9401fa578fadd9647062a207/src/context.ts#L4\r\n\r\nI find this approach weird. The module should ideally not have any global state. We could have an export like `createContext` that would expose all needed methods on it and use its internal context.\r\n\r\nAlso, a global state is wrong because it could end up with the wrong state being used when building multiple fixtures at once.",[],304,"test-utils","Module-level context","2023-12-02T00:18:09Z","https://github.com/nuxt/test-utils/issues/304",{"description":3237,"labels":3245,"number":3137,"owner":3138,"repository":3240,"state":3167,"title":3241,"updated_at":3246,"url":3247,"score":3144},[],"2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/381",{"description":3237,"labels":3249,"number":3250,"owner":3138,"repository":3240,"state":3167,"title":3241,"updated_at":3251,"url":3252,"score":3144},[],455,"2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/455",["Reactive",3254],{},["Set"],["ShallowReactive",3257],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTxpo--Xkb_jOXp6CW928BnbcNgjANErLYTcO7Kcio-U":-1},"/nuxt/icon/354"]