\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```",[3020,3023,3026,3029],{"name":3021,"color":3022},"dx","C39D69",{"name":3024,"color":3025},"bug","d73a4a",{"name":3027,"color":3028},"vite","3574D1",{"name":3030,"color":3031},"馃敤 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.6827975,{"labels":3040,"number":3044,"owner":3033,"repository":3033,"state":3045,"title":3046,"updated_at":3047,"url":3048,"score":3049},[3041],{"name":3042,"color":3043},"2.x","d4c5f9",6376,"closed","Uncaught TypeError: Cannot redefine property: $router","2023-01-18T21:49:10Z","https://github.com/nuxt/nuxt/issues/6376",0.6784791,{"description":3051,"labels":3052,"number":3054,"owner":3033,"repository":3033,"state":3045,"title":3055,"updated_at":3056,"url":3057,"score":3058},"I am trying \r\n\r\n```html\r\n\u003Cnuxt-link v-for=\"action in actions\">{{ action.name }}\u003C/nuxt-link>\r\n```\r\nError\r\n```\r\nTypeError\r\n\r\nCannot read property 'name' of undefined\r\n```\r\n\r\nI tried search `v-for nuxt-link` but can't find the answer.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1854\">#c1854\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3053],{"name":3042,"color":3043},2089,"v-for doesn't work with nuxt-link","2023-01-18T15:43:03Z","https://github.com/nuxt/nuxt/issues/2089",0.6835225,{"description":3060,"labels":3061,"number":3063,"owner":3033,"repository":3033,"state":3045,"title":3064,"updated_at":3065,"url":3066,"score":3067},"Nuxt.js errors on IE10 and IE11 with `Object doesn't support property or method assign`\r\nSee here: https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#Browser_compatibility\r\n\r\nPerhaps some official browser compatibilities could be documented, and some polyfills could be implemented to allow realistic production use of Nuxt.js\r\n\r\nCheers!\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c73\">#c73\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3062],{"name":3042,"color":3043},93,"Browser Compatibility","2023-01-18T15:38:24Z","https://github.com/nuxt/nuxt/issues/93",0.6873191,{"description":3069,"labels":3070,"number":3083,"owner":3033,"repository":3033,"state":3045,"title":3084,"updated_at":3085,"url":3086,"score":3087},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `modules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.1.3`, `@vueuse/nuxt@9.5.0`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-fbh4ex?file=app.vue\r\n\r\n**Please note:** the StackBlitz version doesn't show type errors. If you have a fresh local project with the code, you will see the type error.\n\n### Describe the bug\n\nThe `\u003CHtml>` and `\u003CBody>` components show type errors when you attempt to use anything other than a string for the `class` prop. Shouldn't their `class` prop accept arrays and objects as well?\r\n\r\n```\r\n(property) class?: string | undefined\r\nType '{ test: true; }' is not assignable to type 'string'.ts(2322)\r\ncomponents.d.ts(654, 5): The expected type comes from property 'class' which is declared here on type 'ComponentProps\u003CDefineComponent\u003C{ manifest: StringConstructor; version: StringConstructor; xmlns: StringConstructor; renderPriority: (StringConstructor | NumberConstructor)[]; ... 27 more ...; translate: StringConstructor; }, ... 10 more ..., { ...; }>>'\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3071,3074,3077,3080],{"name":3072,"color":3073},"good first issue","fbca04",{"name":3075,"color":3076},"types","2875C3",{"name":3078,"color":3079},"3.x","29bc7f",{"name":3081,"color":3082},"馃嵃 p2-nice-to-have","0E8A16",15514,"Html and Body components: class prop type error if not string","2023-01-19T17:52:49Z","https://github.com/nuxt/nuxt/issues/15514",0.6889241,{"labels":3089,"number":3094,"owner":3033,"repository":3033,"state":3045,"title":3095,"updated_at":3096,"url":3097,"score":3098},[3090,3093],{"name":3091,"color":3092},"pending triage","E99695",{"name":3042,"color":3043},4683,"TypeError: Cannot read property 'client' of null","2023-01-22T15:30:09Z","https://github.com/nuxt/nuxt/issues/4683",0.6915042,{"description":3100,"labels":3101,"number":3106,"owner":3033,"repository":3033,"state":3045,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v21.2.0\r\n- Nuxt Version: 3.10.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: app, css, devtools, modules, postcss, typescript, ogImage, site, sitemap, routeRules, vite, runtimeConfig, experimental\r\n- Runtime Modules: @nuxt/content@2.11.0, @nuxtseo/module@2.0.0-beta.55\r\n- Build Modules: -\n\n### Reproduction\n\nSwitch from yarn to npm by deleting node_modules and .nuxt folder and reinstall everything with npm i, then start the dev again. I'm using latest vue version with latest nuxt version \n\n### Describe the bug\n\nMy whole project is now plagued with this error, even after switching back to yarn: \r\n\r\n`Property 'xxx' does not exist on type '{}'.ts(2339)`\r\n\r\n\r\n\r\nVolar is correctly setup with the takeover mode. Property and props exist, they are declared correctly. It is very strange.\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3102,3103,3104],{"name":3078,"color":3079},{"name":3091,"color":3092},{"name":3105,"color":3031},"needs reproduction",25607,"Property X does not exist on type '{}'. - TypeScript ","2024-09-21T21:27:40Z","https://github.com/nuxt/nuxt/issues/25607",0.6920642,{"description":3112,"labels":3113,"number":3116,"owner":3033,"repository":3033,"state":3045,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.9.0\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: pnpm@9.1.0\r\n- Builder: -\r\n- User Config: modules, debug, devtools, future, routeRules, vue, imports, content, shadcn, css, colorMode, app, pwa, features, eslint, compatibilityDate\r\n- Runtime Modules: @vueuse/nuxt@10.9.0, @unocss/nuxt@0.61.5, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/color-mode@3.4.1, @vite-pwa/nuxt@0.7.0, @nuxt/eslint@0.3.12, ./modules/shadcn, @nuxt/content@2.13.2\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\node_modules/.pnpm/@nuxtjs+mdc@0.8.3_magicast@0.3.4_rollup@4.18.0/node_modules/@nuxtjs/mdc/dist/runtime/components/prose/ProseImg.vue:15:52 - error TS2339: Property 'useNuxtImage' does not exist on type '{ components: { prose: boolean; map: { p: string; a: string; blockquote: string; \"code-inline\": string; code: string; em: string; h1: string; h2: string; h3: string; h4: string; h5: string; h6: string; hr: string; ... 10 more ...; tr: string; }; }; headings: { ...; }; }'.\r\n\r\n15 const imgComponent = useRuntimeConfig().public.mdc.useNuxtImage ? resolveComponent('NuxtImg') : 'img'\n\n### Describe the bug\n\nWhen I perform `pnpm typecheck`` (\"typecheck\": \"vue-tsc --noEmit\")`, the following error occurs:\r\n\r\n```\r\nnode_modules/.pnpm/@nuxtjs+mdc@0.8.3_magicast@0.3.4_rollup@4.18.0/node_modules/@nuxtjs/mdc/dist/runtime/components/prose/ProseImg.vue:15:52 - error TS2339: Property 'useNuxtImage' does not exist on type '{ components: { prose: boolean; map: { p: string; a: string; blockquote: string; \"code-inline\": string; code: string; em: string; h1: string; h2: string; h3: string; h4: string; h5: string; h6: string; hr: string; ... 10 more ...; tr: string; }; }; headings: { ...; }; }'.\r\n\r\n15 const imgComponent = useRuntimeConfig().public.mdc.useNuxtImage ? resolveComponent('NuxtImg') : 'img'\r\n```\r\n\r\nHowever, I have not used @nuxt/image, and there is no image component in the code. My tsconfig.json is as follows:\r\n```\r\n{\r\n \"extends\": \"./.nuxt/tsconfig.json\",\r\n \"compilerOptions\": {\r\n \"skipLibCheck\": true\r\n },\r\n \"exclude\": [\"node_modules\"]\r\n}\r\n```\r\n\r\nAnd I have tried both TypeScript versions 5.4.5 and 5.5.2, but the error still occurs. How should I fix it?\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3114,3115],{"name":3091,"color":3092},{"name":3105,"color":3031},28359,"Typecheck fail: Property 'useNuxtImage' does not exist on type","2024-08-16T14:09:51Z","https://github.com/nuxt/nuxt/issues/28359",0.6930403,{"labels":3122,"number":3124,"owner":3033,"repository":3033,"state":3045,"title":3125,"updated_at":3126,"url":3127,"score":3128},[3123],{"name":3042,"color":3043},4134,"TS2314: Generic type 'ComponentOptions\u003CV>' requires 1 type argument(s).","2023-01-18T20:03:58Z","https://github.com/nuxt/nuxt/issues/4134",0.69305784,{"description":3130,"labels":3131,"number":3133,"owner":3033,"repository":3033,"state":3045,"title":3134,"updated_at":3135,"url":3136,"score":3137},"# Hi everyone, \r\nwhen I run vue.js aplication with nuxt.js on IE 9+ I get this error 'objects do not support the find property or method ' , in other browsers it work well, someone have any idea ?\r\n\r\n\r\n\r\n \r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c919\">#c919\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3132],{"name":3042,"color":3043},1057,"objects do not support the find property or method ","2023-01-18T15:40:43Z","https://github.com/nuxt/nuxt/issues/1057",0.69367266,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0RD65UTCXYbWQXVtjT0q0K87lBoJIyBL3iL6CFGBhao":-1},"/nuxt/nuxt/1418"]