\n \u003C/template>\n\n \u003Ctemplate #validation>\n \u003CUAlert\n v-if=\"mfaError\"\n color=\"error\"\n icon=\"i-lucide-alert-circle\"\n :title=\"mfaError\"\n class=\"mb-4\"\n />\n \u003C/template>\n\n \u003Ctemplate #footer>\n \u003Cdiv class=\"text-center space-y-2\">\n \u003Cp class=\"text-sm text-gray-600 dark:text-gray-300\">\n Check your authenticator app for the current code.\n \u003C/p>\n \u003CUButton variant=\"ghost\" size=\"sm\" :loading=\"loading\" @click=\"refreshChallenge\">\n \u003CUIcon name=\"i-lucide-refresh-cw\" class=\"h-4 w-4 mr-1\" />\n Get New Code\n \u003C/UButton>\n \u003C/div>\n \u003C/template>\n \u003C/UAuthForm>\n \u003C/UPageCard>\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\n`:fields` is throwing typescript error. Only an issue with `otp`. Looking in\n\n- `node_modules/.pnpm/@nuxt+ui-pro@3.1.3_@babel+parser@7.27.5_db0@0.3.2_better-sqlite3@11.10.0__embla-carouse_48b559106e80aa1b3007fc5d3af2ab7f/node_modules/@nuxt/ui-pro/dist/runtime/components/AuthForm.vue.d.ts`\n- `node_modules/.pnpm/@nuxt+ui@3.1.3_@babel+parser@7.27.5_db0@0.3.2_better-sqlite3@11.10.0__embla-carousel@8._6f36fdd0332a5dab432a961d27814af8/node_modules/@nuxt/ui/dist/runtime/components/PinInput.vue.d.ts`\n- `node_modules/.pnpm/reka-ui@2.3.1_typescript@5.8.3_vue@3.5.16_typescript@5.8.3_/node_modules/reka-ui/dist/index.d.ts`\n \nI'm not seeing what I'm missing. The [docs](https://ui.nuxt.com/components/auth-form#props) don't give any other details than the example.\n\n```\nVue: Type\n{\n name: string;\n type: string;\n placeholder: string;\n otp: {\n length: number;\n placeholder: string;\n };\n}[]\nis not assignable to type AuthFormField[]\nType\n{\n name: string;\n type: string;\n placeholder: string;\n otp: {\n length: number;\n placeholder: string;\n };\n}\nis not assignable to type AuthFormField\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3047,3050,3053,3056,3059,3062],{"name":3048,"color":3049},"bug","d73a4a",{"name":3051,"color":3052},"needs reproduction","CB47CF",{"name":3054,"color":3055},"v3","49DCB8",{"name":3057,"color":3058},"nuxt/ui-pro","00dc82",{"name":3060,"color":3061},"triage","ffffff",{"name":3063,"color":3064},"closed-by-bot","ededed",4317,"ui","UAuthForm otp typescript error","2025-06-18T02:14:57Z","https://github.com/nuxt/ui/issues/4317",0.68861884,{"description":3072,"labels":3073,"number":3077,"owner":3025,"repository":3066,"state":3026,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nI have a form like the following example:\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003Ch1>Training Form\u003C/h1>\n \u003C/div>\n \u003CUForm :state=\"state\" :schema=\"schema\" @submit=\"handleSubmit\">\n \u003CUFormGroup label=\"Name\" name=\"name\">\n \u003CUInput v-model=\"state.name\" />\n \u003C/UFormGroup>\n \u003CUFormGroup label=\"Training Week\" name=\"trainingWeek\">\n \u003Cdiv v-for=\"(day, index) in state.trainingWeek\" :key=\"index\">\n \u003CUFormGroup label=\"Day\" name=\"trainingWeek[' + index + '].day\">\n \u003CUInput v-model=\"day.day\" />\n \u003C/UFormGroup>\n \u003CUFormGroup label=\"Exercises\" name=\"trainingWeek[' + index + '].exercises\">\n \u003Cdiv v-for=\"(exercise, exerciseIndex) in day.exercises\" :key=\"exerciseIndex\">\n \u003CUInput v-model=\"exercise.exerciseName\" />\n \u003C/div>\n \u003C/UFormGroup>\n \u003Cdiv class=\"mt-4 flex justify-end\">\n \u003CUButton @click=\"addExercise(index)\">Add Exercise\u003C/UButton>\n \u003C/div>\n \u003C/div>\n \u003C/UFormGroup>\n \u003Cdiv class=\"mt-4 flex justify-end\">\n \u003CUButton @click=\"addDay\">Add Day\u003C/UButton>\n \u003CUButton type=\"submit\">Submit\u003C/UButton>\n \u003C/div>\n \u003C/UForm>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { z } from \"zod\";\nimport type { FormSubmitEvent } from \"#ui/types\";\nconst state = reactive({\n name: \"\",\n trainingWeek: [\n {\n day: \"\",\n exercises: [\n {\n exerciseName: \"\",\n },\n ],\n },\n ],\n});\n\nconst schema = z.object({\n name: z.string().min(1, \"Required field\"),\n trainingWeek: z.array(\n z.object({\n day: z.string().min(1, \"Required field\"),\n exercises: z.array(\n z.object({\n exerciseName: z.string().min(1, \"Required field\"),\n }),\n ),\n }),\n ),\n});\n\ntype Schema = z.infer\u003Ctypeof schema>;\n\nconst handleSubmit = (event: FormSubmitEvent\u003CSchema>) => {\n console.log(JSON.stringify(event.data, null, 2));\n};\n\nconst addExercise = (index: number) => {\n state.trainingWeek[index].exercises.push({ exerciseName: \"\" });\n};\n\nconst addDay = () => {\n state.trainingWeek.push({ day: \"\", exercises: [{ exerciseName: \"\" }] });\n};\n\u003C/script>\n\n```\n\nI render the form based on state and dynamically add fields.\n\nThe form automatically sets up errors for name ( or any first level fields ) but doesn't set up errors for nested ones like day or exerciseName in the above example\n\nWhat's the proper way to create dynamic forms and avail error setting ? \n\nI'm able to get the following:\n```json\nprofile.vue:68 ZodError: [\n {\n \"code\": \"too_small\",\n \"minimum\": 1,\n \"type\": \"string\",\n \"inclusive\": true,\n \"exact\": false,\n \"message\": \"Required field\",\n \"path\": [\n \"trainingWeek\",\n 0,\n \"day\"\n ]\n },\n {\n \"code\": \"too_small\",\n \"minimum\": 1,\n \"type\": \"string\",\n \"inclusive\": true,\n \"exact\": false,\n \"message\": \"Required field\",\n \"path\": [\n \"trainingWeek\",\n 0,\n \"exercises\",\n 0,\n \"exerciseName\"\n ]\n }\n]\n```\noutput by parsing schema \n```js\nwatchEffect(() => {\n try {\n schema.parse(state);\n } catch (error) {\n console.error(error);\n }\n});\n```\n\n",[3074],{"name":3075,"color":3076},"question","d876e3",2674,"How to ensure UForm and UFormGroup auto assigns errors for nested dynamic form.","2024-11-18T16:59:59Z","https://github.com/nuxt/ui/issues/2674",0.69707584,{"description":3083,"labels":3084,"number":3092,"owner":3025,"repository":3025,"state":3026,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.2\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-zeykrs?file=app.vue\n\n### Describe the bug\n\nAccording to the [example-2](https://nuxt.com/docs/getting-started/error-handling#example-2) in the document, errors cannot be cleared directly. You must access `error.value = null`, which can be seem confusing.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3085,3086,3089],{"name":3019,"color":3020},{"name":3087,"color":3088},"dx","C39D69",{"name":3090,"color":3091},"🍰 p2-nice-to-have","0E8A16",20453,"Using `error = null` in template syntax cannot clear errors","2023-04-29T22:32:30Z","https://github.com/nuxt/nuxt/issues/20453",0.70200753,{"description":3098,"labels":3099,"number":3103,"owner":3025,"repository":3066,"state":3026,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.13.1\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: telemetry, ssr, future, compatibilityDate, modules, hooks, nitro, css, routeRules, devtools, experimental, typescript, imports\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @vueuse/nuxt@13.3.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/suspicious-water-smppjv\n\n### Description\n\nThe docs note that you can access exposed variables from `UForm`. I've found that the following fields are not reactive:\n- dirty \n- dirtyFields\n- blurredFields\n- touchedFields\n\n### Additional context\n\nI see in the [source](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue) that they're not defined with `ref` or `reactive`.\n\nAdditionally, the `dirty` computed that gets exposed would never get updated since `dirtyFields` is not reactive.\n\n### Logs\n\n```shell-script\n\n```",[3100,3101,3102],{"name":3048,"color":3049},{"name":3054,"color":3055},{"name":3060,"color":3061},4238,"Form exposed dirty, dirtyFields, blurredFields, and touchedFields are not reactive","2025-06-24T15:56:14Z","https://github.com/nuxt/ui/issues/4238",0.7024471,{"labels":3109,"number":3114,"owner":3025,"repository":3025,"state":3026,"title":3115,"updated_at":3116,"url":3117,"score":3118},[3110,3111],{"name":3022,"color":3023},{"name":3112,"color":3113},"2.x","d4c5f9",8066,"NuxtJs: ReferenceError: NuxtError is not defined","2023-01-22T15:36:08Z","https://github.com/nuxt/nuxt/issues/8066",0.7036064,{"description":3120,"labels":3121,"number":3126,"owner":3025,"repository":3025,"state":3026,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: modules, css, ssr, devtools, future, typescript, vite, hooks, nitro, compatibilityDate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, nuxt-mikro-orm-module@0.4.1, @nuxt/eslint@1.0.1, nuxt-auth-utils@0.5.15, @nuxt/image@1.9.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nUse this `app.vue`:\n```\n// app.vue\n\u003Cscript setup lang=\"ts\">\n\n\u003C/script>\n\n\u003Ctemplate>\n \u003C!-- https://github.com/nuxt/nuxt/issues/25214#issuecomment-1894051562 -->\n \u003Cdiv>\n \u003CNuxtLoadingIndicator />\n \u003CNuxtRouteAnnouncer />\n\n \u003CNuxtLayout>\n \u003CUApp>\n \u003CNuxtPage />\n \u003C/UApp>\n \u003C/NuxtLayout>\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle>\nbody {\n @apply antialiased;\n background: var(--ui-bg-muted);\n}\n\n.dark {\n body {\n @apply antialiased;\n background: var(--ui-bg);\n }\n}\n\u003C/style>\n```\n\nGo to any page with layout, wait 10-20 sec then try to navigate to another page.\n\n### Describe the bug\n\nSame problem:\nwhen i use navigateTo cant load the page.\nNavigate using user action(navigation menu mouse click) can't load the page\n\n```\n\"nuxt\": \"^3.15.4\",\n\"vue\": \"^3.5.13\",\n\"vue-router\": \"^4.5.0\",\n\"@nuxt/ui\": \"^3.0.0-alpha.10\",\n```\nI get that warning:\n\n\nThen that error:\n\n\nHere is my `app.vue`:\n```\n\u003Cscript setup lang=\"ts\">\n\n\u003C/script>\n\n\u003Ctemplate>\n \u003C!-- https://github.com/nuxt/nuxt/issues/25214#issuecomment-1894051562 -->\n \u003Cdiv>\n \u003CNuxtLoadingIndicator />\n \u003CNuxtRouteAnnouncer />\n\n \u003CNuxtLayout>\n \u003CUApp>\n \u003CNuxtPage />\n \u003C/UApp>\n \u003C/NuxtLayout>\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle>\nbody {\n @apply antialiased;\n background: var(--ui-bg-muted);\n}\n\n.dark {\n body {\n @apply antialiased;\n background: var(--ui-bg);\n }\n}\n\u003C/style>\n```\n\n@TheAlexLichter \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3122,3123,3125],{"name":3022,"color":3023},{"name":3051,"color":3124},"FBCA04",{"name":3063,"color":3064},31010,"Unhandled error during execution of component update, Uncaught (in promise) TypeError: node is null","2025-02-28T02:01:44Z","https://github.com/nuxt/nuxt/issues/31010",0.7048961,{"description":3132,"labels":3133,"number":3142,"owner":3025,"repository":3025,"state":3026,"title":3143,"updated_at":3144,"url":3145,"score":3146},"### Environment\r\n\r\napp\r\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `vite`\r\n- User Config: `extends`, `typescript`, `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\r\n\r\nlayer\r\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `vite`\r\n- User Config: `typescript`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n```\r\n\r\n### Reproduction\r\n\r\n1. clone repo https://github.com/DawidKopys/nuxt-h3-event-ts-error-repro\r\n2. run `npm i` in nuxt-layer directory\r\n3. run `npm i` in app directory\r\n4. run `npx nuxi typecheck` / `npm run dev` / `npx vue-tsc --noEmit` inside app directory. You should get below error:\r\n\r\n```\r\nNuxi 3.6.5 3:57:55 PM\r\n../nuxt-layer/server/api/foo.ts:7:13 - error TS2345: Argument of type 'H3Event' is not assignable to parameter of type 'H3Event\u003CEventHandlerRequest>'.\r\n\r\n7 setCookie(event, 'someCookieName', 'someCookieValue')\r\n ~~~~~\r\n\r\n../nuxt-layer/server/utils/someUtil.ts:6:13 - error TS2345: Argument of type 'H3Event' is not assignable to parameter of type 'H3Event\u003CEventHandlerRequest>'.\r\n Type 'H3Event' is missing the following properties from type 'H3Event\u003CEventHandlerRequest>': method, headers, toJSON, fetch, $fetch\r\n\r\n6 setCookie(event, 'someCookieName', 'someCookieValue')\r\n ~~~~~\r\n\r\n\r\nFound 2 errors in 2 files.\r\n\r\nErrors Files\r\n 1 ../nuxt-layer/server/api/foo.ts:7\r\n 1 ../nuxt-layer/server/utils/someUtil.ts:6\r\n```\r\n\r\n### Describe the bug\r\n\r\n- `app` has dependency `h3` installed with version `1.8.0`\r\n- `nuxt-layer` has dependency `h3` installed with version `1.7.1` (forced with `overrides` field in layer's `package.json` - for simplicity - the effect would be exactly the same if layer had `1.7.1` version locked with its `package-lock.json`)\r\n\r\nAs a result, I am getting typescript errors if **some** utils are imported manually from `h3` and others are auto-imported. Layer file `server/api/foo.ts` shows simple example of this scenario. In this file, `defineEventHandler` is imported manually, while function `setCookie` is auto imported - we get ts error because of that.\r\n\r\nThere is a simple solution for this exact situation - don't import `defineEventHandler` manually. If done so, there are no ts errors for this file.\r\n\r\nHowever, sometimes we might need to import something manually from our dependency. File `server/utils/someUtil.ts` serves as an example of such case.\r\nHere, we have some utility function, which accepts `event` as its argument. In order to type the parameter we need to import `H3Event` from `h3`. This function also uses `setCookie` function which is auto imported.\r\nAgain, we get ts error as a result.\r\n\r\n**Workaround** \r\nImporting everything manually from our `h3` dependency fixes the problem - we no longer get ts errors.\r\nWe no longer get the benefit of auto imports though.\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_",[3134,3137,3138,3139],{"name":3135,"color":3136},"types","2875C3",{"name":3019,"color":3020},{"name":3087,"color":3088},{"name":3140,"color":3141},"layers","006B75",22726,"TypeScript errors when layer and app have different dependency versions","2024-05-24T09:56:28Z","https://github.com/nuxt/nuxt/issues/22726",0.70529157,{"description":3148,"labels":3149,"number":3158,"owner":3025,"repository":3025,"state":3026,"title":3159,"updated_at":3160,"url":3161,"score":3162},"### 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",[3150,3151,3152,3153,3155],{"name":3019,"color":3020},{"name":3048,"color":3049},{"name":3037,"color":3038},{"name":3154,"color":3124},"🔨 p3-minor",{"name":3156,"color":3157},"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.7066097,["Reactive",3164],{},["Set"],["ShallowReactive",3167],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqSiLnVSr8tIAoiRp-fT7CbVnQVEe2qzCA6FZ11-RNU0":-1},"/nuxt/ui/4455"]