\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst page = ref(1)\r\nconst eventTypeFilter = reactive({\r\n options: ['a', 'b', 'c'],\r\n selected: []\r\n})\r\n\r\nconst { data, pending } = await useAsyncData(\r\n 'events',\r\n () => $fetch('/api/events', {\r\n params: {\r\n page: page.value,\r\n eventTypeFilter: eventTypeFilter.selected\r\n }\r\n }),\r\n {\r\n watch: [page, eventTypeFilter.selected]\r\n }\r\n)\r\n\u003C/script>\r\n```\r\n\r\n### Describe the bug\r\n\r\nchoosing a value does not trigger another fetch\r\n\r\n### Additional context\r\n\r\nIf I use a ref array for the model and pass that to the watcher, it works\r\n`const selectedEventTypes = ref([])`\r\n\r\n### Logs\r\n\r\n_No response_",[2892,2895],{"name":2893,"color":2894},"3.x","29bc7f",{"name":2868,"color":2869},27261,"closed","Reactive object does not trigger asyncData","2024-05-17T11:17:05Z","https://github.com/nuxt/nuxt/issues/27261",0.67528737,{"description":2903,"labels":2904,"number":2910,"owner":2871,"repository":2871,"state":2897,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Environment\r\n\r\nNuxi 3.0.0\r\nNuxt project info :\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `modules`, `css`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.2.0`, `nuxt-icon@0.1.8`, `@pinia/nuxt@0.4.6`, `@nuxtjs/supabase@0.3.0`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nThe reproduction didn't work\r\n\r\n### Describe the bug\r\n\r\nI have created a little app. When I go to my page by a NuxtLink I have no error, but when I reload it, this error is displayed :\r\n\r\n\r\nNote that this error occurs only on this specific page and I try to call onMounted function and I have the same error: onMounted is not defined\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell\r\n[Vue warn]: Unhandled error during execution of setup function \r\n at \u003CGenerator onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > >\r\n```\r\n",[2905,2906,2907],{"name":2893,"color":2894},{"name":2868,"color":2869},{"name":2908,"color":2909},"needs reproduction","FBCA04",12547,"500 - watch is not defined at _sfc_main.setup","2023-01-24T14:41:14Z","https://github.com/nuxt/nuxt/issues/12547",0.67849344,{"description":2916,"labels":2917,"number":2920,"owner":2871,"repository":2871,"state":2897,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: ignore, modules, supabase, css, app, vite\r\n- Runtime Modules: nuxt-icon@0.5.0, @unocss/nuxt@0.56.1, @nuxtjs/supabase@1.1.2, @nuxtjs/color-mode@3.3.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nVue playground [[link](https://play.vuejs.org/#eNqNU01v2zAM/SuELo5Rwx7Qm+sE24octsM2dDvq4im069aWDIlOAwT+76XkJHXatOjBH+J7fHqkqL341vfpdkCRi8Ip2/QEDmnoV1I3XW8swR4sVgm/SkXNFhN4KkndHz7rqkJFMEJlTQcRC0U3UkutjHasRCXhnU+E5UlgsQdlBk05fIExZvYZtwrM6g0p7LZ4EUxgEcNyxSztTItpa+oZGsc3kGVAtqlrtO5VOlfzbnKVbst2wDjhujeIfc4iA3oPFwSn6hdvxSKc+hJqziFKZq247O0TUtVc6OjztdixnUbfto165G5OknupYWYiDd29uuLOnsIHyTPozInyiriJ/HmM/BTZNDE8K7wg7PqWhXgFUPwfiIyGryFnKcXBjxQrQkdFNuHMLbJZokgEOd6zaur0wRnNUxmMS6FM1zct2t89NexJinwqyWNl25qnnyHmDys5xtU9qscL8Qe38zEp/lh0aLcoxQmj0tZIE7z++wt3/H8CO7MZWmZ/AN4h92vwHifa90Fv2PaMF9z+CHer0fU/t94Rancsyhv1zDHwpeAbdftB6S92r9PrkMdHI8ZnXQJLPw==)]\r\nNuxt repro [[link](https://stackblitz.com/edit/github-q8xcd1?file=app.vue)]\r\n\r\n### Describe the bug\r\n\r\nI noticed some watchEffects in my application did not seem to be triggering. I thought it was a vue problem, but seeking help from the community, it seems that it was not an issue with vue itself. Then I was able to verify that the same effects indeed ran normally on vue, but not on nuxt.\r\n\r\nI was capable of reproducing it within the playgrounds. Here is the basic snippet of code I am using:\r\n\r\n```vue\r\n\u003Cscript setup>\r\nimport { ref, reactive, watch, watchEffect } from 'vue';\r\n\r\nconst stateReact = reactive({ count: 0 });\r\nconst stateRef = ref({ count: 0 });\r\nwatch(stateReact, () => console.log(stateReact)); // triggers\r\nwatch(stateRef, () => console.log(stateRef.value), { deep: true }); // triggers\r\nwatchEffect(() => console.log('effect react: ', stateReact)); // do not trigger on nuxt\r\nwatchEffect(() => console.log('effect ref: ', stateRef.value)); // do not trigger on nuxt\r\n\r\nconst onClick = () => {\r\n stateReact.count++;\r\n stateRef.value.count++;\r\n console.log('clicked');\r\n};\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cbutton @click=\"onClick\">test\u003C/button>\r\n\u003C/template>\r\n```\r\n\r\nThe expected behavior: When clicking the button, 4 logs should be printed to the console.\r\n\r\nBut on nuxt, the watchEffects logs don't trigger. You can see that by opening the dev tools and watching the console on the repros.\r\n\r\nWith nuxt:\r\n\r\nhttps://github.com/nuxt/nuxt/assets/54607854/0030b818-9851-4fe0-9a0e-c4675a3e9f8c\r\n\r\nWith vue:\r\n\r\nhttps://github.com/nuxt/nuxt/assets/54607854/cf20a26d-ed7a-4b46-8596-98c92d66cb50\r\n\r\nI am assuming it is an issue, since it behaves differently.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2918,2919],{"name":2893,"color":2894},{"name":2868,"color":2869},23628,"watchEffect is not triggering with reactive or ref objects","2023-10-18T19:57:30Z","https://github.com/nuxt/nuxt/issues/23628",0.6838938,{"description":2926,"labels":2927,"number":2933,"owner":2871,"repository":2871,"state":2897,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Environment\n\n- Operating System: Darwin\n- Node Version: v21.6.2\n- Nuxt Version: 3.13.0\n- CLI Version: 3.13.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: devtools, experimental, runtimeConfig, routeRules, app, css, plugins, modules, device, googleFonts, primevue, tailwindcss, compatibilityDate, vite\n- Runtime Modules: @nuxt/image@1.7.0, @pinia/nuxt@0.5.4, @primevue/nuxt-module@4.0.5, @nuxtjs/tailwindcss@6.12.1, @nuxtjs/google-fonts@3.2.0, @nuxt/content@2.13.2, @nuxtjs/device@3.2.2\n- Build Modules: -\n\n### Reproduction\n\n\n```\nconst requestParams = reactive({\n limit: 48,\n});\n\nconst { data, refresh, status } = await useLazyFetch\u003Cany>(\n 'https://api.site.com/api/orders',\n {\n query: requestParams,\n }\n);\n\nwatch(\n () => data.value,\n (newValue) => {\n if (newValue) {\n console.log(\"ads\");\n orders.value.push(...(newValue?.orders || []));\n }\n },\n {\n immediate: true,\n }\n);\n```\n\n### Describe the bug\n\nWhen I navigate through NuxtLink, the watch triggers twice, if I just reload the pages, then once. When I remove immediate: true, then when the page is reloaded, the watch does not work and the data is not written to orders, but if I go through NuxtLink, it works 1 time\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2928,2929,2930],{"name":2868,"color":2869},{"name":2908,"color":2909},{"name":2931,"color":2932},"closed-by-bot","ededed",29605,"Nuxt 3 SSR. Watch fires twice if lazy: true","2025-02-19T02:00:25Z","https://github.com/nuxt/nuxt/issues/29605",0.6924906,{"labels":2939,"number":2944,"owner":2871,"repository":2871,"state":2897,"title":2945,"updated_at":2946,"url":2947,"score":2948},[2940,2943],{"name":2941,"color":2942},"question","cc317c",{"name":2893,"color":2894},12791,"computed value not updating?","2023-01-19T16:35:11Z","https://github.com/nuxt/nuxt/issues/12791",0.6977305,{"description":2950,"labels":2951,"number":2957,"owner":2871,"repository":2871,"state":2897,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment (stackblitz)\n\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cwy9wkvf-akwpyxym?file=app.vue\n\n### Describe the bug\n\nThis bug is similar to #31896 but it appears under different conditions.\nAlso, it appears in Nuxt v3.17.4, but not v3.17.3. So, probably some regression between these 2 versions introduced it.\n\nTo reproduce the bug: open the reproduction link and type one character into the input field. You will see the error:\n\n```\nError: [GET] \"/api/ping?q=a\": \u003Cno response> Request aborted as another request to the same endpoint was initiated.\n```\n\nIf you open the `Network` tab in the browser's devtools, you will also see that 2 requests were fired: first is fired and then aborted, then second is fired and successful. This is obviously unexpected as the parameter was changed only once.\n\nIf you will type more characters into the `input` field, all further requests will be successful and not duplicatied anymore. Only the very first request after page loading is bugged.\n\nAlso, if you remove `watch` from the `app.vue`, the bug also doesn't appear.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2952,2954],{"name":2953,"color":2909},"🔨 p3-minor",{"name":2955,"color":2956},"possible regression","B90A42",32233,"useFetch error when watcher exists","2025-06-02T17:32:02Z","https://github.com/nuxt/nuxt/issues/32233",0.7016508,{"description":2963,"labels":2964,"number":2971,"owner":2871,"repository":2972,"state":2897,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAs of now, in Nuxt UI v3.0.0-alpha.x, the `SIDE_OPTIONS` constant is defined as follows:\n\n``` ts\nconst SIDE_OPTIONS: [\"top\", \"right\", \"bottom\", \"left\"];\n```\n\nThe current four directions cannot meet the practical development needs. For example, when there is a button on the far right of the screen to open a dropdown menu, it cannot automatically appear as 'bottom-right'.Tooltips, dropdown menus, or popovers may require positioning beyond the basic cardinal directions to avoid obscuring content or to better fit within the viewport.\n\n#### Proposed Enhancement\n\nI propose to extend the SIDE_OPTIONS constant to include combinations of the cardinal directions to allow for greater flexibility and finer control over positioning. The updated SIDE_OPTIONS would be:\n\n``` ts\nconst SIDE_OPTIONS = [\n \"top\", \"right\", \"bottom\", \"left\",\n \"bottom-left\", \"bottom-right\",\n \"left-top\", \"left-bottom\",\n \"top-left\", \"top-right\",\n \"right-top\", \"right-bottom\"\n];\n```\n\n\n### Additional context\n\n| | |\n| ----------- | ----------- |\n|  | |\n\n\n",[2965,2968],{"name":2966,"color":2967},"enhancement","a2eeef",{"name":2969,"color":2970},"v3","49DCB8",2712,"ui","Side needs more direction","2024-11-20T19:59:29Z","https://github.com/nuxt/ui/issues/2712",0.7021715,{"description":2978,"labels":2979,"number":2986,"owner":2871,"repository":2871,"state":2897,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: devtools, modules, runtimeConfig, devServer, plugins, vue, app, typescript, compatibilityDate, hooks\n- Runtime Modules: @nuxt/eslint@0.7.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-95rtqeeh?file=pages%2Fpage2.client.vue\n\n### Describe the bug\n\nWhen the value of a variable is immediately updated within a Promise callback in the setup function as shown below, the change is not reflected in the v-model of the input.\nThis issue only occurs when running in CSR mode, such as in index.client.vue.\nIt does not occur when running the exact same source code in index.vue.\nAdditionally, this issue does not occur in Vue projects that do not use Nuxt.\n\n```vue\n\u003Cscript setup>\nconst msg = ref('')\n\nmsg.value = 'Changed1' // OK\n\nPromise.resolve().then(() => {\n msg.value = 'Changed2' // NG (not reflect for v-model)\n})\n\nsetTimeout(() => {\n msg.value = 'Changed3' // OK\n}, 2000)\n\u003C/script>\n\n\u003Ctemplate>\n msg: {{ msg }}\n \u003Cinput v-model=\"msg\" />\n\u003C/template>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2980,2983],{"name":2981,"color":2982},"upstream-bug","B60205",{"name":2984,"color":2985},"✨ good reproduction","fbca04",30590,"Variable changes are not reflected in v-model in certain case","2025-02-09T18:08:58Z","https://github.com/nuxt/nuxt/issues/30590",0.7022226,["Reactive",2992],{},["Set"],["ShallowReactive",2995],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3ktIC40DnodwkUjXSj5SWzBrhECdo7wIIhV89f9HRiw":-1},"/nuxt/nuxt/27454"]