\r\n \u003C/form>\r\n \u003C/div>\r\n \u003Cdiv>total: {{ patients?.meta?.total }}\u003C/div>\r\n \u003Cul v-if=\"!pending\">\r\n \u003Cli v-for=\"patient in patients.data\" :key=\"patient.id\">\r\n # {{ patient.id }} | {{ patient.name }}\r\n \u003C/li>\r\n \u003C/ul>\r\n \u003Cdiv v-else>loading ...\u003C/div>\r\n \u003Cdiv class=\"flex justify-center space-x-2\">\r\n \u003Cbutton\r\n @click=\"goToPage(number)\"\r\n v-for=\"number in 4\"\r\n :key=\"number\"\r\n class=\"text-xs border border-green rounded-lg bg-gray-200 text-black px-2 py-1\"\r\n >\r\n {{ number }}\r\n \u003C/button>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n``` \n\n### Describe the bug\n\nThe [watch] option inside usefetch composable isn't working, it only works when using useAsyncData with $fetch.\r\nthe page and keyword parameters are always in initial value, watch dosn't trigger the reactive values.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2064,2065],{"name":2014,"color":2015},{"name":2017,"color":2018},21883,"[watch] option inside useFetch composable isn't working properly","2023-07-01T18:58:28Z","https://github.com/nuxt/nuxt/issues/21883",0.70214105,{"description":2072,"labels":2073,"number":2075,"owner":1988,"repository":1988,"state":2023,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### Environment\r\n\r\nStackblitz\r\n\r\n### Reproduction\r\n\r\n1. Open [Vue Playground Link](https://play.vuejs.org/#eNp9U1tP2zAU/itHfmk6lRQoT12pxrY+MImLBtsLRlOanBSDY2eOXYqq/PcdO2nacakURcc+1+87n9fsrCzjpUM2ZpMqNaK0UKF15ZQrUZTaWFiDwXwAz4lNH2Z5jqmFGnKjC+hRXq+Lu3j5pslSqGzrjoc7d74JBXOValVZsFjZM2Pg1FeP7tYgsjEcQT2gft483pqjrXkC9X2fq51ZoqgPp1PwRbXEWOpF1JaOl4l0OIDe1a/bm/Pvs16fMifDBiTBo4PFopSJRToBTHYBLA8KnaEc+1oHiTGnnLVlOYMhxU+GXTIbsFc4X5MJMlELX6LibJfYjzj9zJV9KRFuqeXV/JFIauArV8zRQP2WxAxzofDCzzxps+7up1Gvjeh5Ag3+dcIg1bHGIdREB1e5U6kVWoErMwJDscnLTGJBSCKhMlxtug5AqFyP4ToxViRdl2kf1p69/0i/C5n3fm7vA4jj+L2AQef1tcOJsNG3AZjh3C1++wyq1Wz6nTmPN/K4SOxDnEutTRRMk6hMF5T36ejwsN8ifiueMOQ+BZ1fNgKivdT+t09FmVgGg8y5s5aY/ZJKkT7R+rdoggx8DMANktrCXZM0bLJa/3rdLbkmXry/abCjP65IgbYiALlYxI+VVqS/gImzlGQpJJqr0i+Z5DferISzREr9/CPceUG0y6CcB0yf3rl/rFb+jrNrgxWaJaHofDYxC7SNe3ZziSuyOyc9JScpeo/zJxL5zs/YhH11KqOxd+LCtOfh5Qi1uK1mK4uq2oDygwb5hHjO6BX5F/kR9O24o3i0kR2x+GeJxtckAkfxSTwasfof0HG4/Q==)\r\n2. Click on \"Set value\"\r\n3. Check the console and see that watchEffect was triggered (\"outside\" and \"inside\")\r\n\r\nNow with Nuxt 🙈 \r\n\r\n1. Open the [Stackblitz](https://stackblitz.com/edit/nuxt-issues-28240)\r\n2. Click on \"Set Value\"\r\n3. Check the console -> watchEffect **was not triggered**, neither \"outside\" nor \"inside\"\r\n\r\n### Describe the bug\r\n\r\nI am not sure why the behavior is different than in plain Vue but somehow, even with `ssr: false`, the update event of `defineModel` is never fired when using an array ref as value and modifying an element of the array.\r\n\r\n### Additional context\r\n\r\nusing `watch` + `deep` (in either inside or outside) will trigger properly.\r\n\r\n### Logs\r\n\r\n_No response_",[2074],{"name":2017,"color":2018},28240,"defineModel behavior for `ref` arrays differs from plain Vue","2024-07-22T08:30:11Z","https://github.com/nuxt/nuxt/issues/28240",0.70615965,{"description":2081,"labels":2082,"number":2086,"owner":1988,"repository":2005,"state":2023,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### 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",[2083,2085],{"name":2032,"color":2084},"a2eeef",{"name":2051,"color":2052},2712,"Side needs more direction","2024-11-20T19:59:29Z","https://github.com/nuxt/ui/issues/2712",0.7067187,{"description":2092,"labels":2093,"number":2098,"owner":1988,"repository":1988,"state":2023,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### Version\n\n[v2.5.1](https://github.com/nuxt.js/releases/tag/v2.5.1)\n\n### Reproduction link\n\n[https://github.com/lhaggarty/hotpotato](https://github.com/lhaggarty/hotpotato)\n\n### Steps to reproduce\n\nDist folder in repo\n\n\n\n. The default index.vue page has @click events that call method (changeStep), a data watch listener (step). These work in dev and production mode, but don't in generate files. I have console.log at the start of both the method and watch function. Neither console.log show up then running /index.html generated page.\n\n### What is expected ?\n\nIn my build, the area below the \"next\" or \"previous\" button has visual changes within the html elements, or the elements are changed. For example: \n\n\n\u003CExportButtonBar2 v-if=\"step > 7\">\u003C/ExportButtonBar2>\n \u003CVideoPlayerAndSidebar v-if=\"step > 2\">\u003C/VideoPlayerAndSidebar>\n\n### What is actually happening?\n\nNothing happens. Methods doesn't seem to trigger, and the watch data value isn't triggered.\n\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9049\">#c9049\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2094,2095],{"name":2017,"color":2018},{"name":2096,"color":2097},"2.x","d4c5f9",5537,"Event Listener / method / watch data not working after Nuxt Generate","2023-01-22T15:33:04Z","https://github.com/nuxt/nuxt/issues/5537",0.70735437,{"description":2104,"labels":2105,"number":2108,"owner":1988,"repository":1988,"state":2023,"title":2109,"updated_at":2110,"url":2111,"score":2112},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-zdl7ze?file=pages%2Findex.vue\n\n### Describe the bug\n\nI'm new to Vue/Nuxt and maybe this is something really obvious but I'm seeing something that makes no sense to me:\r\n\r\n\u003Cimg width=\"515\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/337968/159bebd0-27df-4670-87c9-82e60236db83\">\r\n\r\nThe red container has an `v-if=\"data.pending\"` on it. My understanding is that this should mean the element is hidden when the value is false. That does not happen, I can see the `false` value rendered **inside** the element. \r\n\r\nThe code is very small:\r\n\r\n```ts\r\n\u003Cscript setup lang=\"ts\">\r\nconst data = useAsyncData('test', async () => {\r\n return 'test';\r\n});\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv style=\"background: red\" v-if=\"data.pending\">\r\n Pending is: {{ data.pending }}, Data is: {{ data.data }}\r\n \u003C/div>\r\n \u003Cdiv style=\"background: red\" v-if=\"false\">This is false\u003C/div>\r\n \u003Cdiv style=\"background: green\" v-if=\"true\">This is true\u003C/div>\r\n\u003C/template>\r\n```\n\n### Additional context\n\nThis happens locally (MacOS) and in stackblitz\n\n### Logs\n\n_No response_",[2106,2107],{"name":2014,"color":2015},{"name":2017,"color":2018},26683,"v-if does not work with useAsyncData","2024-04-07T19:34:25Z","https://github.com/nuxt/nuxt/issues/26683",0.70786333,["Reactive",2114],{},["Set"],["ShallowReactive",2117],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"lg0sudCNosk2xVTEn-w2WUEsUyAFt-agf5OmUsGxj0Q":-1},"/nuxt/fonts/356"]