\r\n\t\t\u003CNuxt />\r\n\t\t\u003CFhFooter />\r\n\t\u003C/main>\r\n\u003C/template>\r\n...\r\n```\r\n\r\n**components/FhHeader.vue**\r\n```\r\n\u003Ctemplate>\r\n\t\u003Cheader>\r\n \t...\r\n\t\t\u003CFhSnippetMenu name=\"mainmenu\"/>\r\n \t ...\r\n\t\u003C/header>\r\n\u003C/template>\r\n...\r\n```\r\n\r\n**components/FhSnippetMenu.vue**\r\nThis is the component that fetches the data asynchronously\r\n```\r\n\u003Ctemplate>\r\n\t\u003CFhContent :items=\"items\">\u003C/FhContent>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\n\texport default {\r\n\t\tname: 'FhSnippetMenu',\r\n\t\tprops: [\"name\"],\r\n\t\t\r\n\t\tdata () {\r\n\t\t\treturn {\r\n\t\t\t\titems: []\r\n\t\t\t}\r\n\t\t},\r\n\r\n\t\tasync fetch() {\r\n\t\t\tthis.items = (await this.$wagtail.menus.$name(this.name)).items;\r\n\t\t},\r\n\t\t...\r\n```\r\n\r\n**components/FhContent.vue**\r\nIt uses this component to render the list of content\r\n```\r\n\u003Ctemplate>\r\n\t\u003Cdiv class=\"fh-streamfield\">\r\n\t\t\u003Ctemplate v-for=\"(item, index) in items\">\r\n\t\t\t\u003Cspan> item.title\u003C/span>\r\n\t\t\u003C/template>\r\n\t\u003C/div>\r\n\u003C/template>\r\n\u003Cscript>\r\n\texport default {\r\n\t\tname: 'FhContent',\r\n\t\tprops: [\"items\"]\r\n\t}\r\n\u003C/script>\r\n...\r\n```\r\n\r\n### What is Expected?\r\n\r\nThe HTML markup that is rendered server side is looking correct. The component is populated with the dynamic content. Surprisingly when I move the `\u003CFhHeader/>` BELOW the `\u003CNuxt />` Component, everything is working fine! However, when I remove the `\u003CNuxt/>` component entirely from the default layout, the error occurs again. \r\n\r\nAnother thing I noticed is that when I wrap the `\u003CFhContent>` inside the FhSnippetMenu.vue component inside another wrapper div things are working fine and as expected! But this can obviously not be the proper solution...\r\n\r\n**components/FhSnippetMenu.vue**\r\nThis would work fine...\r\n```\r\n\u003Ctemplate>\r\n\t\u003Cdiv>\r\n\t\t\u003CFhContent :items=\"items\">\u003C/FhContent>\r\n\t\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nAny help would be much appreciated because I am dealing with this issue for 3 days now... Thank you in advance!\r\n",[2942,2943],{"name":2867,"color":2868},{"name":2870,"color":2871},9073,"Hydration of components with fetchHook in the layout scope will fail","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/9073",0.65194404,{"description":2950,"labels":2951,"number":2955,"owner":2873,"repository":2873,"state":2874,"title":2956,"updated_at":2916,"url":2957,"score":2958},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: \u003C!-- ex: v2.13.0 --> 2.15.4\r\n- node: \u003C!-- ex: v12.14.0 --> 12.20.1\r\n\r\n### Reproduction\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\nhttps://github.com/Machine-Maker/nuxt-dev-reload-issue\r\nhttps://codesandbox.io/s/nuxt-dev-reload-issue-mk16j\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\nImportant files\r\n* middleware/test.ts\r\n* pages/test/other.vue\r\n* store/index.ts\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\nOk, so steps to reproduce\r\n1. Clone repo\r\n2. `yarn install`\r\n3. `yarn dev`\r\n4. navigate to http://localhost:4000/test/other\r\n5. go to pages/test/other.vue\r\n6. find the commented out bit on line 48 and uncomment it (the purpose of this, is to trigger the hot module reload)\r\n7. error on reload, saying `arr` is undefined. \r\nThere are some logging statements which show that asyncData is **not** being finished before the component is rendered (so `arr` is indeed undefined)\r\n\r\n### What is Expected?\r\nthe component should not be rendered until asyncData is finished\r\n\r\n### What is actually happening?\r\nBest I can figure, the store commit in `middleware/test.ts` is causing the issue. Comment out that line, and everything works. Idk like anything about the inner workings of nuxt/vue/vuex but I think it's the updating of that vuex state that causes the issue.",[2952,2953,2954],{"name":2882,"color":2883},{"name":2867,"color":2868},{"name":2870,"color":2871},9130,"Nuxt Dev: hot reload - asyncData called after component rendered","https://github.com/nuxt/nuxt/issues/9130",0.65207726,{"description":2960,"labels":2961,"number":2964,"owner":2873,"repository":2873,"state":2874,"title":2965,"updated_at":2916,"url":2966,"score":2967},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.15.3\r\n- node: 12.18.1\r\n\r\n### Reproduction\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\nIf I am trying to preview a page that is not already generated, the order of method execution is not guaranteed like the server side.\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\nIn my case, I fetch some global data in `nuxtServerInit` that depends on the `asyncData` of my page component.\r\nIf the page is already generated in the `generate` process no problems are encountered, but I am trying to preview a new page (not already generated) it will call asyncData before nuxtServerInit (or at the same time, but no waiting for nuxtServerInit).\r\n\r\n### What is Expected?\r\nI expect to keep the order like server-side execution so the `asyncData` has to wait for the nuxtServerInit completion.\r\n\r\n### What is actually happening?\r\nActually both methods are called but no order is guaranteed (so I get an error).",[2962,2963],{"name":2867,"color":2868},{"name":2870,"color":2871},9173,"nuxt preview methods order in static mode","https://github.com/nuxt/nuxt/issues/9173",0.6529713,["Reactive",2969],{},["Set"],["ShallowReactive",2972],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f63Fh48gn3YTxnxSBIY4ruh8c4F-ZgSRtY3ricmSgg6M":-1},"/nuxt/nuxt/8150"]