`\n\nit doesn't work that way\n\nI really ask for help!",[2887,2890],{"name":2888,"color":2889},"question","d876e3",{"name":2871,"color":2872},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.70843863,{"description":2897,"labels":2898,"number":2908,"owner":2877,"repository":2877,"state":2909,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Environment\n\nNuxt project info: 15:46:56\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[reproduction](https://stackblitz.com/github/jbreuil/layout-repro)\r\n\r\nIn this reproduction, the error is triggered when the layout is changed on routing. The error start appearing when adding a ref element in the component. The ref is on a v-for following the [documentation syntax](https://vuejs.org/guide/essentials/template-refs.html#refs-inside-v-for) and [typing](https://vuejs.org/guide/typescript/composition-api.html#typing-template-refs)\n\n### Describe the bug\n\nRelated to #13309, where people have the same error when using Transition.\r\n\r\nHere the error is the same and triggered at the same time (change of layout on routing to another page). In this reproduction, the error is appearing once we add a ref in the v-for of the component.\r\n\r\nFixed if you downgrade to nuxt 3.3.3\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2899,2902,2905],{"name":2900,"color":2901},"3.x","29bc7f",{"name":2903,"color":2904},"pending triage","E99695",{"name":2906,"color":2907},"upstream","E8A36D",21323,"closed","Layout error when using an Element ref on v-for","2023-07-06T15:39:03Z","https://github.com/nuxt/nuxt/issues/21323",0.6724107,{"description":2915,"labels":2916,"number":2918,"owner":2877,"repository":2877,"state":2909,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/content@2.13.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-mzb2e5\r\n\r\nOpen the console and click on the \"Link\".\r\n\r\n### Describe the bug\r\n\r\nIf you create a composable with `useLazyAsyncData` and then call it inside `ClientOnly` component it will log the below warning when you want to navigate between pages:\r\n\r\n```\r\nchunk-2XHGWBZJ.js?v=008d553a:1512 [Vue warn]: Slot \"default\" invoked outside of the render function: this will not track dependencies used in the slot. Invoke the slot function inside the render function instead. \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C Proxy(Object) {…} > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n```\r\n\r\n### Additional context\r\n\r\nUsing `useLazyAsyncData` directly inside the component is Okay and works without problem.\r\n\r\n### Logs\r\n\r\n_No response_",[2917],{"name":2900,"color":2901},27752,"Slot \"default\" invoked outside of the render function when using a composable (contains useLazyAsyncData) inside ClientOnly component","2024-06-24T10:03:48Z","https://github.com/nuxt/nuxt/issues/27752",0.6815308,{"labels":2924,"number":2927,"owner":2877,"repository":2877,"state":2909,"title":2928,"updated_at":2929,"url":2930,"score":2931},[2925,2926],{"name":2900,"color":2901},{"name":2903,"color":2904},14465,"Template refs can only be addressed correctly during initial loading","2023-01-19T17:35:46Z","https://github.com/nuxt/nuxt/issues/14465",0.6839626,{"description":2933,"labels":2934,"number":2940,"owner":2877,"repository":2878,"state":2909,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### Environment\n\nI just use the demo component on nuxt ui page\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nI recorded it, you can see my vid:\n\nhttps://github.com/user-attachments/assets/82b444d5-473f-43b3-b26f-55b30cc61184\n\n### Description\n\nIt happens when a select box is opening.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2935,2938,2939],{"name":2936,"color":2937},"bug","d73a4a",{"name":2871,"color":2872},{"name":2874,"color":2875},3261,"I saw some flickering with the select boxes in a form","2025-03-08T13:57:49Z","https://github.com/nuxt/ui/issues/3261",0.68481165,{"description":2946,"labels":2947,"number":2957,"owner":2877,"repository":2877,"state":2909,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nReproduction : https://stackblitz.com/edit/github-88hbfa?file=pages%2Findex.vue\r\n\r\nSteps to reproduce:\r\n1. In a page file, retrieve data using `useAsyncData` and display an array of elements in the template using this data.\r\n2. Assign the array of elements to a ref variable as described in the Vue.js documentation: https://vuejs.org/guide/essentials/template-refs.html#accessing-the-refs.\r\n3. Display this page in a browser.\r\n4. Edit the JS code of this page (e.g., modify console.log).\r\n5. Errors will appear.\r\n\r\nThis error does not occur if:\r\n- The page is being shown for the first time (no reloading through JS edits).\r\n- The code specified above is inside app.vue and not inside a page that is loaded with NuxtPage (if you copy/paste index.vue inside app.vue, errors do not occur).\r\n- No ref is used\r\n- `useAsyncData` is not used\r\n\r\n### Describe the bug\r\n\r\nConsole error is shown related to scheduler flush.\r\nAlso, `TypeError: Cannot read properties of null (reading 'parentNode')` error is thrown.\r\nSee Logs field for more detials about these errors\r\n\r\n### Workarounds\r\n\r\n- Reload page (meh)\r\n- Use `reactive` instead of `ref`\r\n```html\r\n\u003Ctemplate>\r\n\u003Cdiv>\r\n \u003Cli v-for=\"menuItem in menuItems\" ref=\"(el) => updateMenuItemRefs(el)\">\u003C/li>\r\n\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n[...]\r\nconst menuItemRefs = reactive([])\r\nfunction updateMenuItemRefs (el) {\r\n menuItemRefs.push(el)\r\n}\r\n\u003C/script>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n(initially made with `test.vue` page, but error is the same)\r\n\r\n```shell-script\r\ntest.vue:14 edit this message 2\r\n\r\nchunk-3Q27KRJ5.js:97 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core \r\n at \u003CRouteProvider key=\"/test\" routeProps= {Component: {…}, route: {…}} pageKey=\"/test\" ... > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\nwarn @ chunk-3Q27KRJ5.js:97\r\nlogError @ chunk-3Q27KRJ5.js:271\r\nhandleError @ chunk-3Q27KRJ5.js:263\r\ncallWithErrorHandling @ chunk-3Q27KRJ5.js:215\r\nflushJobs @ chunk-3Q27KRJ5.js:411\r\nPromise.then (async)\r\nqueueFlush @ chunk-3Q27KRJ5.js:324\r\nqueueJob @ chunk-3Q27KRJ5.js:318\r\nreload @ chunk-3Q27KRJ5.js:517\r\n(anonymous) @ chunk-3Q27KRJ5.js:547\r\n(anonymous) @ test.vue?t=1688346524889:81\r\n(anonymous) @ client.ts:542\r\n(anonymous) @ client.ts:459\r\n(anonymous) @ client.ts:306\r\nqueueUpdate @ client.ts:306\r\nawait in queueUpdate (async)\r\n(anonymous) @ client.ts:159\r\nhandleMessage @ client.ts:157\r\n(anonymous) @ client.ts:90\r\nShow 7 more frames\r\n\r\nchunk-MNWBZQKJ.js:82 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n at parentNode (chunk-MNWBZQKJ.js:82:30)\r\n at ReactiveEffect.componentUpdateFn [as fn] (chunk-3Q27KRJ5.js:5823:11)\r\n at ReactiveEffect.run (reactivity.esm-bundler.js:178:19)\r\n at instance.update (chunk-3Q27KRJ5.js:5860:52)\r\n at callWithErrorHandling (chunk-3Q27KRJ5.js:213:32)\r\n at flushJobs (chunk-3Q27KRJ5.js:411:9)\r\nparentNode @ chunk-MNWBZQKJ.js:82\r\ncomponentUpdateFn @ chunk-3Q27KRJ5.js:5823\r\nrun @ reactivity.esm-bundler.js:178\r\ninstance.update @ chunk-3Q27KRJ5.js:5860\r\ncallWithErrorHandling @ chunk-3Q27KRJ5.js:213\r\nflushJobs @ chunk-3Q27KRJ5.js:411\r\nPromise.then (async)\r\nqueueFlush @ chunk-3Q27KRJ5.js:324\r\nqueueJob @ chunk-3Q27KRJ5.js:318\r\nreload @ chunk-3Q27KRJ5.js:517\r\n(anonymous) @ chunk-3Q27KRJ5.js:547\r\n(anonymous) @ test.vue?t=1688346524889:81\r\n(anonymous) @ client.ts:542\r\n(anonymous) @ client.ts:459\r\n(anonymous) @ client.ts:306\r\nqueueUpdate @ client.ts:306\r\nawait in queueUpdate (async)\r\n(anonymous) @ client.ts:159\r\nhandleMessage @ client.ts:157\r\n(anonymous) @ client.ts:90\r\nShow 8 more frames\r\n```\r\n",[2948,2949,2950,2951,2954],{"name":2900,"color":2901},{"name":2936,"color":2937},{"name":2906,"color":2907},{"name":2952,"color":2953},"🔨 p3-minor","FBCA04",{"name":2955,"color":2956},"suspense","C70109",21901,"Unhandled error during execution of scheduler flush related to NuxtPage, useAsyncData & refs ","2024-07-22T19:43:53Z","https://github.com/nuxt/nuxt/issues/21901",0.6855306,{"description":2963,"labels":2964,"number":2968,"owner":2877,"repository":2969,"state":2909,"title":2970,"updated_at":2971,"url":2972,"score":2973},"When trying to mount component with `mountSuspended` component can't emit anything.\r\n\r\nEven if I explicitly emit in `\u003Cscript setup>`, `wrapper.emitted()` object is always equal to `{}`.",[2965],{"name":2966,"color":2967},"vitest-environment","b60205",527,"test-utils","mountSuspended doesn't support emits","2023-12-02T00:17:07Z","https://github.com/nuxt/test-utils/issues/527",0.69190526,{"description":2975,"labels":2976,"number":2979,"owner":2877,"repository":2878,"state":2909,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\n\n.\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nGo to https://ui3.nuxt.dev/getting-started and change the theme to dark and the neutral color to neutral.\n\n### Description\n\nI just entered the site and had the preference to see the docs with neutral colors and in dark mode and now seems that the last update on the docs brokes the dark mode with neutral color. I tested it in multiple browsers and looks the same.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/f79b85ea-a40a-4f97-9c81-f36735d1eebb\n\n### Logs\n\n```shell-script\n\n```",[2977,2978],{"name":2936,"color":2937},{"name":2871,"color":2872},3399,"Dark mode with neutral color seems to be broken in the v3 UI docs","2025-03-22T15:51:05Z","https://github.com/nuxt/ui/issues/3399",0.6937274,{"labels":2985,"number":2990,"owner":2877,"repository":2877,"state":2909,"title":2991,"updated_at":2992,"url":2993,"score":2994},[2986,2989],{"name":2987,"color":2988},"documentation","5319e7",{"name":2900,"color":2901},13402,"Slot can't be root-element in layouts","2023-01-19T16:54:59Z","https://github.com/nuxt/nuxt/issues/13402",0.6957834,["Reactive",2996],{},["Set"],["ShallowReactive",2999],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fS8rvvSF2RnQc3lbkRe8kTcRxZuWvVUQtMKw8eKMxQZE":-1},"/nuxt/ui/3023"]