\n\n3) Navigate to `pages/index.vue`, modify the `console.log()` and save\n\n### Describe the bug\n\nThe previous [issue](https://github.com/nuxt/nuxt/issues/25214) was closed, but the error remains even in the latest Nuxt version.\n\nThe error will disappear if you add `lazy:true` option\n\n```\nconst { data } = await useFetch('https://jsonplaceholder.typicode.com/todos/1', {\n lazy: true\n})\n```\n\nAs you can see, both `app.vue` `layouts/default.vue` are wrapped with `divs` as it was suggested in the previous issue but we still get the bug.\n\nIs adding `lazy` option is the best workaround as for now?\n\n\u003Cimg width=\"500\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ca5929e7-f84b-4d0f-a57b-e1cf38c34813\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nvirtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16 [Vue warn]: Unhandled error during execution of component update \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CDefault ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js:51\nlogError @ runtime-core.esm-bundler.js:263\nhandleError @ runtime-core.esm-bundler.js:255\ncallWithErrorHandling @ runtime-core.esm-bundler.js:201\nflushJobs @ runtime-core.esm-bundler.js:408\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js:322\nqueueJob @ runtime-core.esm-bundler.js:317\neffect2.scheduler @ runtime-core.esm-bundler.js:5448\ntrigger @ reactivity.esm-bundler.js:253\nendBatch @ reactivity.esm-bundler.js:311\nnotify @ reactivity.esm-bundler.js:597\ntrigger @ reactivity.esm-bundler.js:571\nset value @ reactivity.esm-bundler.js:1448\nfinalizeNavigation @ vue-router.mjs:3498\n(anonymous) @ vue-router.mjs:3363\nPromise.then\npushWithRedirect @ vue-router.mjs:3330\npush @ vue-router.mjs:3255\nreplace @ vue-router.mjs:3258\naddRoutes @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16\n(anonymous) @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:21\n(anonymous) @ client:34\n(anonymous) @ client:208\n(anonymous) @ client:183\nqueueUpdate @ client:183\nawait in queueUpdate\n(anonymous) @ client:884\nhandleMessage @ client:882\nonMessage @ client:299\n(anonymous) @ client:429\ndispatchEvent @ .localservice@runtime.5a421e5b.js:26\n_handleMessage @ .localservice@runtime.5a421e5b.js:26\n_0x3963e2 @ .localservice@runtime.5a421e5b.js:26Understand this warningAI\nruntime-dom.esm-bundler.js:51 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\n at parentNode (runtime-dom.esm-bundler.js:51:30)\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5410:11)\n at ReactiveEffect.run (reactivity.esm-bundler.js:225:19)\n at ReactiveEffect.runIfDirty (reactivity.esm-bundler.js:263:12)\n at callWithErrorHandling (runtime-core.esm-bundler.js:199:33)\n at flushJobs (runtime-core.esm-bundler.js:408:9)\n```",[2856,2859,2862,2865],{"name":2857,"color":2858},"dx","C39D69",{"name":2860,"color":2861},"bug","d73a4a",{"name":2863,"color":2864},"vite","3574D1",{"name":2866,"color":2867},"🔨 p3-minor","FBCA04",31493,"nuxt","open","TypeError: Cannot read properties of null (reading 'parentNode') with useFetch","2025-03-21T17:04:23Z","https://github.com/nuxt/nuxt/issues/31493",0.64131063,{"labels":2876,"number":2882,"owner":2869,"repository":2869,"state":2883,"title":2884,"updated_at":2885,"url":2886,"score":2887},[2877,2880,2881],{"name":2878,"color":2879},"3.x","29bc7f",{"name":2860,"color":2861},{"name":2866,"color":2867},12746,"closed","Meta Components reports Cannot read properties of null (reading'$nuxt') error","2023-01-19T16:16:27Z","https://github.com/nuxt/nuxt/issues/12746",0.64578545,{"description":2889,"labels":2890,"number":2900,"owner":2869,"repository":2869,"state":2883,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.14.0`\r\n- Nuxt Version: `3.2.0`\r\n- Nitro Version: `2.2.1`\r\n- Package Manager: `yarn@1.22.15`\r\n- Builder: `vite`\r\n- User Config: `app`, `modules`, `components`, `build`, `googleFonts`, `headlessui`, `runtimeConfig`\r\n- Runtime Modules: `@nuxt/devtools@0.1.2`, `@nuxtjs/tailwindcss@6.4.0`, `@nuxt/image-edge@1.0.0-27919678.2f5b64b`, `@nuxtjs/google-fonts@3.0.0-1`, `@vueuse/nuxt@9.12.0`, `nuxt-headlessui@1.1.1`, `nuxt-icon@0.1.8`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\napp/router.options.ts\r\n```ts\r\nimport type { RouterConfig } from \"@nuxt/schema\";\r\nexport default \u003CRouterConfig>{\r\n routes: () => [\r\n {\r\n name: \"repair\",\r\n path: \"/:brand/repair/\",\r\n component: () => import(\"~/pages/repair/index.vue\"),\r\n },\r\n {\r\n name: \"repair-model\",\r\n path: \"/:brand/repair/model/:model/\",\r\n component: () => import(\"~/pages/repair/model.vue\"),\r\n },\r\n ],\r\n};\r\n```\r\n\r\npages/repair/index.vue\r\n```js\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CSectionA :data=\"getSectionData('hero')\" />\r\n \u003CSectionB :data=\"getSectionData('prices')\" />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nconst brand = useBrand();\r\n\r\nconst { data, error } = await useFetch(\"/api/v1/repair\", {\r\n params: { brand },\r\n});\r\n\r\nconst getSectionData = (sectionId) => {\r\n return data.value.data.blocks.find((block) => block.id === sectionId);\r\n};\r\n\u003C/script>\r\n```\r\n\r\nserver/api/v1/repair/index.get.js\r\n```js\r\nimport hero from \"@/data/hero.json\";\r\nimport prices from \"@/data/prices.json\";\r\n\r\nexport default defineEventHandler(async (event) => {\r\n const { brand } = getQuery(event);\r\n\r\n /* ... use brand ... */\r\n\r\n return {\r\n data: {\r\n blocks: [\r\n {\r\n id: \"hero\",\r\n title: hero.title,\r\n data: hero.data,\r\n },\r\n {\r\n id: \"prices\",\r\n title: prices.title,\r\n data: prices.data,\r\n },\r\n ],\r\n },\r\n };\r\n});\r\n```\n\n### Describe the bug\n\nAfter update page i get error and strange behavior of data - caching. After refresh page i get old data. Helps - restarting the project, but the error with extracting data remains.\n\n### Additional context\n\n```js\r\nruntime-core.esm-bundler.js:40 [Vue warn]: Unhandled error during execution of render function \r\n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \r\n at \u003CRouteProvider key=\"/tesla/repair/\" routeProps= {Component: {…}, route: {…}} pageKey=\"/tesla/repair/\" ... > \r\n at \u003CFragmentWrapper > \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CApp key=2 > \r\n at \u003CNuxtRoot>\r\n\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'data')\r\n at Proxy.getSectionData (index.vue:89:1)\r\n at Proxy._sfc_render (index.vue:96:1)\r\n at renderComponentRoot (runtime-core.esm-bundler.js:914:44)\r\n at hydrateSubTree (runtime-core.esm-bundler.js:5621:44)\r\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5642:25)\r\n at ReactiveEffect.run (reactivity.esm-bundler.js:190:25)\r\n at instance.update (runtime-core.esm-bundler.js:5763:56)\r\n at setupRenderEffect (runtime-core.esm-bundler.js:5777:9)\r\n at runtime-core.esm-bundler.js:1506:17\r\n```\n\n### Logs\n\n_No response_",[2891,2892,2895,2898],{"name":2878,"color":2879},{"name":2893,"color":2894},"pending triage","E99695",{"name":2896,"color":2897},"windows","C681FD",{"name":2899,"color":2867},"needs reproduction",19030,"Cannot read properties of null (reading 'data')","2024-03-12T07:00:40Z","https://github.com/nuxt/nuxt/issues/19030",0.6513184,{"description":2906,"labels":2907,"number":2914,"owner":2869,"repository":2915,"state":2883,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Description\n\n\nHow to set v-model type of UCalendar\n`\n \u003CUCalendar\n v-model=\"datePickerValue\"\n range\n size=\"lg\"\n color=\"error\"\n weekday-format=\"short\"\n >\n \u003Ctemplate #heading=\"{ value }\">\n \u003Cdiv class=\"custom-heading\">\n \u003Ch2 class=\"text-sm font-medium text-[#3f3f3f] leading-tight\">\n {{ formatMonthYear(value) }}\n \u003C/h2>\n \u003C/div>\n \u003C/template>\n\n \u003C!-- Day 커스터마이즈 -->\n \u003Ctemplate #day=\"{ day }\">\n \u003Cdiv class=\"custom-day\">\n \u003Cspan\n :class=\"{\n 'text-sm font-semibold': isDaySelected(day),\n 'text-sm font-normal': !isDaySelected(day),\n }\"\n >{{ extractDay(day) }}\u003C/span\n >\n \u003C/div>\n \u003C/template>\n\n \u003Ctemplate #week-day=\"{ day }\">\n \u003Cdiv class=\"custom-week-day bg-white border-none\">\n \u003Cspan class=\"font-medium text-xs text-[#7e7e7e]\">{{ day }}\u003C/span>\n \u003C!-- 예시: 요일을 간단하게 출력 -->\n \u003C/div>\n \u003C/template>\n \u003C/UCalendar>\n`\n\n`const datePickerValue = ref\u003C{ start: DateValue; end: DateValue }>({\n start: new CalendarDate(\n new Date().getFullYear(),\n new Date().getMonth() + 1,\n new Date().getDate()\n ) as DateValue,\n end: new CalendarDate(\n new Date().getFullYear(),\n new Date().getMonth() + 1,\n new Date().getDate()\n ) as DateValue,\n});`\n\nI put the above variable in v-model, but I get the following error. How should I declare the type?\n\n`'{ start: { readonly calendar: { identifier: string; fromJulianDay: (jd: number) => CalendarDate; toJulianDay: (date: AnyCalendarDate) => number; getDaysInMonth: (date: AnyCalendarDate) => number; ... 8 more ...; isInverseEra?: ((date: AnyCalendarDate) => boolean) | undefined; }; ... 11 more ...; compare: (b: AnyCale...' 형식은 'DateRange' 형식에 할당할 수 없습니다.\n 'start' 속성의 형식이 호환되지 않습니다.\n '{ readonly calendar: { identifier: string; fromJulianDay: (jd: number) => CalendarDate; toJulianDay: (date: AnyCalendarDate) => number; getDaysInMonth: (date: AnyCalendarDate) => number; ... 8 more ...; isInverseEra?: ((date: AnyCalendarDate) => boolean) | undefined; }; ... 11 more ...; compare: (b: AnyCalendarDate)...' 형식은 'DateValue | undefined' 형식에 할당할 수 없습니다.\n '{ readonly calendar: { identifier: string; fromJulianDay: (jd: number) => CalendarDate; toJulianDay: (date: AnyCalendarDate) => number; getDaysInMonth: (date: AnyCalendarDate) => number; ... 8 more ...; isInverseEra?: ((date: AnyCalendarDate) => boolean) | undefined; }; ... 11 more ...; compare: (b: AnyCalendarDate)...' 형식은 'DateValue | undefined' 형식에 할당할 수 없습니다.\n '{ readonly calendar: { identifier: string; fromJulianDay: (jd: number) => CalendarDate; toJulianDay: (date: AnyCalendarDate) => number; getDaysInMonth: (date: AnyCalendarDate) => number; ... 8 more ...; isInverseEra?: ((date: AnyCalendarDate) => boolean) | undefined; }; ... 11 more ...; compare: (b: AnyCalendarDate)...' 형식에 'ZonedDateTime' 형식의 #private, hour, minute, second 외 4개 속성이 없습니다.ts-plugin(2322)\nCalendar.vue(99, 3): 필요한 형식은 여기에서 '{ readonly \"onUpdate:modelValue\"?: ((date: DateRange | null) => any) | undefined; readonly \"onUpdate:placeholder\"?: ((...args: unknown[]) => any) | undefined; readonly \"onUpdate:startValue\"?: ((date: DateValue | undefined) => any) | undefined; ... 36 more ...; prevPage?: ((placeholder: DateValue) => DateValue) | und...' 형식에 선언된 'modelValue' 속성에서 가져옵니다.`",[2908,2911],{"name":2909,"color":2910},"question","d876e3",{"name":2912,"color":2913},"v3","49DCB8",3900,"ui","How to set v-model type of UCalendar","2025-04-25T06:07:41Z","https://github.com/nuxt/ui/issues/3900",0.6529429,{"description":2921,"labels":2922,"number":2930,"owner":2869,"repository":2869,"state":2883,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-ax2aaa\n\n### Describe the bug\n\nWhen using NuxtLink to navigate from the root component to another page, a TypeError: Cannot read properties of null (reading 'parentNode') error occurs. This bug appeared after Vue version 3.4.32.\r\n\r\n\n\n### Additional context\n\n#### Conditions Triggering the Bug:\r\n\r\nThe error occurs when a Teleport component does not have a v-if condition for mounting. During page navigation, if Teleport is used without a v-if condition, the error is triggered.\r\n\r\n#### Conditions Not Triggering the Bug:\r\n\r\nThe error does not occur if a v-if condition is added to the Teleport component.\r\n\r\nThe issue seems to be caused by a change introduced in Vue version 3.4.32, where hostRemove(targetStart!) was added. This can be referenced in the following commit: [Commit 8655ced](https://github.com/vuejs/core/commit/8655ced480ea0fe453ff5fe445cecf97b91ec260#diff-030bd876734dc84e37752a562874250fd76eb083242b96a7774adb7a44f77872R275).\r\n\n\n### Logs\n\n_No response_",[2923,2926,2927],{"name":2924,"color":2925},"upstream","E8A36D",{"name":2899,"color":2867},{"name":2928,"color":2929},"upstream-bug","B60205",28274,"Cannot read properties of null (reading 'parentNode') when navigate from page","2024-07-24T05:15:17Z","https://github.com/nuxt/nuxt/issues/28274",0.6545078,{"labels":2936,"number":2940,"owner":2869,"repository":2869,"state":2883,"title":2941,"updated_at":2942,"url":2943,"score":2944},[2937,2938,2939],{"name":2878,"color":2879},{"name":2893,"color":2894},{"name":2899,"color":2867},14078,"vue-router error","2023-01-19T17:24:12Z","https://github.com/nuxt/nuxt/issues/14078",0.657045,{"description":2946,"labels":2947,"number":2955,"owner":2869,"repository":2915,"state":2883,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Description\n\nI’ve been using USlideover from NuxtUI (v3), and I noticed that there’s no event triggered when clicking on the overlay (outside of the slideover). This makes it tricky to detect when a user dismisses it by clicking outside, rather than using the close button.\n\nIt would be super helpful if USlideover emitted an event whenever it’s closed—whether that’s via the close button or the overlay. That way, we could easily handle any necessary logic when the slideover is dismissed.\n\nIf exposing a close event isn’t feasible, maybe the overlay could be made accessible as a slot? That way, we could wrap it in our own template and attach a @click event directly. This would give us more flexibility in handling interactions.\n\nI took a look at the source code, and it seems like these interactions are already handled internally, but they aren’t exposed as events:\n🔗 [Slideover.vue](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Slideover.vue)\n\nWould be awesome to see this in a future update.\n\n### Additional context\n\n_No response_",[2948,2951,2952],{"name":2949,"color":2950},"enhancement","a2eeef",{"name":2912,"color":2913},{"name":2953,"color":2954},"triage","ffffff",3225,"Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.6596143,{"labels":2961,"number":2969,"owner":2869,"repository":2869,"state":2883,"title":2970,"updated_at":2971,"url":2972,"score":2973},[2962,2963,2966,2967,2968],{"name":2878,"color":2879},{"name":2964,"color":2965},"workaround available","11376d",{"name":2860,"color":2861},{"name":2924,"color":2925},{"name":2928,"color":2929},13309,"TypeError: Cannot read properties of null (reading 'parentNode')","2025-02-17T17:13:12Z","https://github.com/nuxt/nuxt/issues/13309",0.66026026,{"labels":2975,"number":2982,"owner":2869,"repository":2869,"state":2883,"title":2983,"updated_at":2984,"url":2985,"score":2986},[2976,2977,2978,2979],{"name":2878,"color":2879},{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2980,"color":2981},"🍰 p2-nice-to-have","0E8A16",14477,"Cannot read properties of null (reading 'getAttribute') infinite log loop","2023-01-19T17:36:00Z","https://github.com/nuxt/nuxt/issues/14477",0.6611747,{"description":2988,"labels":2989,"number":2993,"owner":2869,"repository":2869,"state":2883,"title":2994,"updated_at":2995,"url":2996,"score":2997},"**reproduction**: https://stackblitz.com/edit/github-cmeky2-mysxox\r\n\r\n```\r\n[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 \u003CNuxtRoot>\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\r\n```\r\n\r\nContext: https://github.com/nuxt/nuxt.js/issues/13788",[2990,2991,2992],{"name":2878,"color":2879},{"name":2860,"color":2861},{"name":2866,"color":2867},14693,"errors when navigating back and forth from error pages","2023-04-25T15:13:24Z","https://github.com/nuxt/nuxt/issues/14693",0.66324294,["Reactive",2999],{},["Set"],["ShallowReactive",3002],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fr5pGIc0BADPrHnTB7eIB8SfefcqRpVfUeIfiikF5L1k":-1},"/nuxt/ui/3543"]