\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```",[2921,2924,2927,2930],{"name":2922,"color":2923},"dx","C39D69",{"name":2925,"color":2926},"bug","d73a4a",{"name":2928,"color":2929},"vite","3574D1",{"name":2931,"color":2932},"🔨 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.62861973,{"description":2941,"labels":2942,"number":2952,"owner":2934,"repository":2934,"state":2935,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nThe error occurs when I go to the third level child page, then back to the second and then go to the page with await inside\r\n\r\nReproduction: https://stackblitz.com/edit/nuxt-issues-24991-tlw3yk\r\n\r\nInstructions for reproducing the bug:\r\n\r\n 1. INDEX PAGE must be initial\r\n\r\n 2. Go to SETTING/PROJECT PAGE\r\n\r\n 3. Go to SETTING/PROJECT/CREATE PAGE\r\n\r\n 4. Go to SETTING/PROJECT PAGE\r\n\r\n 5. Go to WAITING PAGE\r\n\r\n 6. Look in console (error due to waiting)\r\n\r\n\r\nErrors in console: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'namespaceURI') Uncaught (in promise) TypeError: Cannot read properties of null (reading 'exposed')\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nAn error is thrown though navigation should work as usual\r\n\r\n### Additional context\r\n\r\nReported by @ilyaDegtyarenko in https://github.com/nuxt/nuxt/discussions/23221\r\n\r\nThis issue is not solved by Vue 3.4.X nor Nuxt 3.9\r\n\r\n### Logs\r\n\r\n_No response_",[2943,2946,2949],{"name":2944,"color":2945},"pending triage","E99695",{"name":2947,"color":2948},"upstream","E8A36D",{"name":2950,"color":2951},"suspense","C70109",24991,"Navigating from twice-nested Nuxt page to async page throws error","2024-06-30T11:06:27Z","https://github.com/nuxt/nuxt/issues/24991",0.66034615,{"description":2958,"labels":2959,"number":2966,"owner":2934,"repository":2934,"state":2967,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### 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```",[2960,2961,2963],{"name":2944,"color":2945},{"name":2962,"color":2932},"needs reproduction",{"name":2964,"color":2965},"closed-by-bot","ededed",31010,"closed","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.6418956,{"description":2973,"labels":2974,"number":2979,"owner":2934,"repository":2934,"state":2967,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.1`\r\n- Nuxt Version: `3.4.0`\r\n- Nitro Version: `2.3.3`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `ssr`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nI created a new Nuxt application using `npx nuxi init project-ssr-false`\r\n\r\nThen ran `npm install`\r\n\r\nThe only change I made was in **nuxt.config.ts**:\r\n```ts\r\n// https://nuxt.com/docs/api/configuration/nuxt-config\r\nexport default defineNuxtConfig({\r\n ssr: false\r\n})\r\n```\r\n\r\nThen `npm run dev` \r\n\r\nHere is a repo with the configuration specified above that reproduces the issue: https://github.com/justinwride/project-ssr-false\r\n\r\n### Describe the bug\r\n\r\nThe bug is a blank white page when I expected to see my Nuxt application.\r\n\r\nAfter navigating to http://localhost:3000 I get the following console errors:\r\n\u003Cimg width=\"512\" alt=\"image\" src=\"https://user-images.githubusercontent.com/32500970/231534495-112f4e80-3c0b-4e7a-8717-b7745b73249e.png\">\r\n\r\n### Additional context\r\n\r\nThis error *does not happen* on version `3.3.3`. It is a new error with version `3.4.0`.\r\n\r\nThe line that appears to be failing is this:\r\n```js\r\nconst nuxt = createNuxtApp({ vueApp });\r\n```\r\n\r\nWhich is failing because of this line:\r\n```js\r\nconst runtimeConfig = process.server ? options.ssrContext.runtimeConfig : reactive(nuxtApp.payload.config);\r\n```\r\n\r\nIt appears that `nuxtApp.payload.config` is `undefined` \r\n\r\n### Logs\r\n\r\n```shell-script\r\nentry.js:39 value cannot be made reactive: undefined\r\ncreateReactiveObject @ vue.js?v=2e04f03c:1090\r\nreactive @ vue.js?v=2e04f03c:1076\r\ncreateNuxtApp @ nuxt.js?v=33afac7b:97\r\ninitApp @ entry.js:39\r\n(anonymous) @ entry.js:57\r\nShow 3 more frames\r\nentry.js:58 Error while mounting app: TypeError: Cannot create proxy with a non-object as target or handler\r\n at createNuxtApp (nuxt.js?v=33afac7b:98:1)\r\n at initApp (entry.js:39:18)\r\n at entry.js:57:3\r\n(anonymous) @ entry.js:58\r\nPromise.catch (async)\r\n(anonymous) @ entry.js:57\r\n```\r\n",[2975,2978],{"name":2976,"color":2977},"3.x","29bc7f",{"name":2944,"color":2945},20240,"Nuxt Starter Project no longer works when SSR is false on 3.4.0","2023-04-12T17:52:59Z","https://github.com/nuxt/nuxt/issues/20240",0.6467192,{"labels":2985,"number":2988,"owner":2934,"repository":2934,"state":2967,"title":2989,"updated_at":2990,"url":2991,"score":2992},[2986,2987],{"name":2976,"color":2977},{"name":2944,"color":2945},14254,"/_nuxt paths don't work behind Apache reverse proxy","2023-01-19T17:31:13Z","https://github.com/nuxt/nuxt/issues/14254",0.6481651,{"labels":2994,"number":2997,"owner":2934,"repository":2934,"state":2967,"title":2998,"updated_at":2999,"url":3000,"score":3001},[2995,2996],{"name":2976,"color":2977},{"name":2944,"color":2945},13438,"Nuxt 3 one tier setup breaks after version 3.0.0-27375411.b38e394","2023-01-19T16:56:15Z","https://github.com/nuxt/nuxt/issues/13438",0.6495326,{"labels":3003,"number":3006,"owner":2934,"repository":2934,"state":2967,"title":3007,"updated_at":3008,"url":3009,"score":3010},[3004,3005],{"name":2976,"color":2977},{"name":2944,"color":2945},14223,"when adding the module, request error in `nuxi dev`","2023-01-19T17:30:47Z","https://github.com/nuxt/nuxt/issues/14223",0.652874,{"labels":3012,"number":3022,"owner":2934,"repository":2934,"state":2967,"title":3023,"updated_at":3024,"url":3025,"score":3026},[3013,3014,3017,3018,3019],{"name":2976,"color":2977},{"name":3015,"color":3016},"workaround available","11376d",{"name":2925,"color":2926},{"name":2947,"color":2948},{"name":3020,"color":3021},"upstream-bug","B60205",13309,"TypeError: Cannot read properties of null (reading 'parentNode')","2025-02-17T17:13:12Z","https://github.com/nuxt/nuxt/issues/13309",0.65460795,{"description":3028,"labels":3029,"number":3032,"owner":2934,"repository":2934,"state":2967,"title":3033,"updated_at":3034,"url":3035,"score":3036},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v19.4.0 // tried also 19.1, 19.9, 18.4\r\n- Nuxt Version: 3.4.3 // tried also 3.5.1\r\n- Nitro Version: 2.4.1 //tried also 2.3.3\r\n- Package Manager: yarn@2.4.3 //tried also NPM and yarn@1\r\n- Builder: vite\r\n- User Config: preset, server, loadingIndicator, css, app, modules, i18n, vite, nitro, experimental\r\n- Runtime Modules: @nuxtjs/i18n@8.0.0-beta.12\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nI an trying to create a repro but could not undestand what I need to do for it.\r\n\r\nI did\n\n### Describe the bug\n\nnpx nuxt build\r\n\r\n````\r\n//log from linux machine\r\n✔ Generated public .output/public nitro 9:42:02 PM\r\nℹ Initializing prerenderer nitro 9:42:03 PM\r\n\r\n ERROR Error: The service is no longer running: write EPIPE nitro 9:42:04 PM\r\n\r\n\r\n// same code, build on Windows\r\nwhy the proxy module need for prerender? how to remove it from this step ?\r\n\r\n\r\ni Initializing prerenderer nitro 21:43:01\r\n[21:43:21] i [HPM] Proxy created: ... \r\ni Prerendering 1 routes nitro 21:43:21\r\n\r\n[21:43:21] ERROR (node:29456) Warning: To load an ES module, set \"type\": \"module\" in the package.json or use the .mjs extension.\r\n(Use node --trace-warnings ... to show where the warning was created)\r\n\r\n\r\n[21:43:21] ERROR [nuxt] [request error] [unhandled] [500] Cannot use import statement outside a module\r\n at internalCompileFunction (node:internal/vm:73:18)\r\n at wrapSafe (node:internal/modules/cjs/loader:1195:20)\r\n at Module._compile (node:internal/modules/cjs/loader:1239:27)\r\n at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)\r\n at Module.load (node:internal/modules/cjs/loader:1133:32)\r\n at Module._load (node:internal/modules/cjs/loader:972:12)\r\n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/translators:165:29)\r\n at ModuleJob.run (node:internal/modules/esm/module_job:193:25)\r\n\r\n ├─ /__i18n__/prerender/365c1add.js (157ms) (Error: [500] ) nitro 21:43:21\r\ni Building Nitro Server (preset: node-server) nitro 21:43:21\r\n\r\n ERROR RangeError: Maximum call stack size exceeded nitro 21:45:01\r\n\r\n\r\nundefined\r\n\r\n\r\n ERROR Maximum call stack size exceeded 21:45:01\r\n\r\n at applyProductionCondition (/E:/inetpub/inn/nuxt3b/node_modules/nitropack/dist/shared/nitro.a3c42e5a.mjs:713:3)\r\n at applyProductionCondition (/E:/inetpub/inn/nuxt3b/node_modules/nitropack/dist/shared/nitro.a3c42e5a.mjs:724:5)\r\n```\r\n\r\n\n\n### Additional context\n\nExiting (working) install .\r\nTested on windows and on linux.\r\n\r\nThe old logs from the working build did not do the `prerender` step. the configuration did not use the prerender as I am using SPA/SSR depending on the needs.\r\n\r\n\r\nWhat I was tried before opening the bug:\r\nyarn, npm redownload again and again\r\nremove modules and build\r\ntried to build with nuxt/nuxi 3.4.1, 3.5.1, 3.4.2\r\ntried diffrent node / OS versions.\r\ntried to connect debugger to see where is the crash (code)\r\ntried to add a logging code to `applyProductionCondition`\r\n\r\n\r\n\r\n\n\n### Logs\n\n```shell-script\nThanks for all !! we are using nuxt and happy with it.\n```\n",[3030,3031],{"name":2976,"color":2977},{"name":2947,"color":2948},21051,"prerendering crashes with `@nuxtjs/i18n`","2023-07-12T14:54:46Z","https://github.com/nuxt/nuxt/issues/21051",0.654884,{"description":3038,"labels":3039,"number":3042,"owner":2934,"repository":2934,"state":2967,"title":3043,"updated_at":3044,"url":3045,"score":3046},"### Environment\r\n\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.13.1`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `npm@8.1.2`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `target`, `app`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\n1. create a new project by using `npx nuxi init nuxt-app`\r\n2. edit nuxt.config.ts as below\r\n```\r\nimport { defineNuxtConfig } from 'nuxt'\r\n// https://v3.nuxtjs.org/api/configuration/nuxt.config\r\nexport default defineNuxtConfig({\r\n ssr: false,\r\n target: 'static',\r\n app: {\r\n baseURL: '/',\r\n }\r\n})\r\n```\r\n3. `npm run build`\r\n4. deploy `.outopt/public/*` on web server root (linux server using Apache)\r\n\r\n### Describe the bug\r\n\r\nWhen accessing the server on the browser, no contents are shown on the page and I can see several errors.\r\n\r\n* error 1: \r\n ```\r\n GET https://example.com/index.html/_payload.js net::ERR_ABORTED 404\r\n ```\r\n* error 2: \r\n ```\r\n Refused to apply style from 'https://example.com/_nuxt/entry.3571d144.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.\r\n ```\r\n* error 3: \r\n ```\r\n entry.7d6d0124.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'baseURL')\r\n at fa (entry.7d6d0124.js:1:65263)\r\n at entry.7d6d0124.js:1:100806\r\n ```\r\n\r\nIs there any miss-settings on the nuxt.config.ts?\r\n\r\n### Additional context\r\n\r\nI could deploy by the same way until `3.0.0-rc.5`.\r\n\r\n### Logs\r\n\r\n_No response_",[3040,3041],{"name":2976,"color":2977},{"name":2944,"color":2945},14908,"console errors occur when build with no-ssr mode","2023-01-19T17:42:26Z","https://github.com/nuxt/nuxt/issues/14908",0.6551334,["Reactive",3048],{},["Set"],["ShallowReactive",3051],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbmG8QL13gTNqFhwxB_jR5_HO15_cpZ-TR9YWx4z5MbM":-1},"/nuxt/nuxt/28019"]