\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\n export default {name: \"x-div\"}\r\n\u003C/script>\r\n```\r\n\r\n\r\npages/index.vue\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cdiv>hello\u003C/div>\r\n \u003C!--\u003Cdiv v-if=\"onClient\">ladies and\u003C/div>-->\r\n \u003Cx-div v-if=\"onClient\">gentlemen\u003C/x-div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\n import XDiv from \"@/components/x-div\"\r\n\r\n export default {\r\n components: {XDiv},\r\n data: () => ({onClient: typeof window !== \"undefined\"}),\r\n }\r\n\u003C/script>\r\n```\r\n\r\nstep to reproduce:\r\n- `npm i`\r\n- `npm run dev`\r\n- access localhost:3000\r\n\r\nnote :\r\n- uncommenting `\u003C!--\u003Cdiv v-if=\"onClient\">ladies and\u003C/div>-->` make the x-div patch successfull \r\n:ok:\r\n```\r\n\u003Cdiv v-if=\"onClient\">ladies and\u003C/div>\r\n\u003Cx-div v-if=\"onClient\">gentlemen\u003C/x-div>\r\n```\r\n- :beetle:\r\n```\r\n\u003Cx-div v-if=\"onClient\">gentlemen\u003C/x-div>\r\n\u003Cdiv v-if=\"onClient\">ladies and\u003C/div>\r\n```\r\n\r\n## workaround\r\nif bug does not occure in a library component, it is possible to move the vif on a div surrounding the component : `\u003Cx-div v-if=\"onClient\">gentlemen\u003C/x-div>` => `\u003Cdiv v-if=\"v-if=\"onClient\">\u003Cx-div >gentlemen\u003C/x-div>\u003C/div>`\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7360\">#c7360\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[1984],{"name":1985,"color":1986},"2.x","d4c5f9",3514,"nuxt","closed","error when patching content on client side only","2023-01-18T16:24:10Z","https://github.com/nuxt/nuxt/issues/3514",0.5165701,{"description":1995,"labels":1996,"number":1998,"owner":1988,"repository":1988,"state":1989,"title":1999,"updated_at":2000,"url":2001,"score":2002},"The recent upgrade to vue 2.5.10 causes hydration errors in my app (commit [4cf855](https://github.com/nuxt/nuxt.js/commit/4cf855ce8115fb17447f2b69fa312237642bbef5)):\r\n\r\n`The client-side rendered virtual DOM tree is not matching server-rendered content.`\r\n\r\nThe error is:\r\n```\r\n[nuxt] Error while initializing app TypeError: Cannot read property 'toLowerCase' of undefined\r\nat emptyNodeAt (vue.runtime.esm.js?ff9b:5127)\r\n...\r\n```\r\n\r\nIt seems that `nodeOps.tagName(elm)` is `undefined`, and that `elm` (if chrome devtools is to be believed) is an empty comment node here:\r\n\r\n```\r\n\u003Cdiv id=\"__nuxt\">\r\n \u003Cdiv class=\"nuxt-progress\" style=\"width:0%;height:2px;background-color:#0275d8;opacity:0;\">\u003C/div>\r\n \u003C!---->\r\n\u003C/div>\r\n```\r\n\r\nAny idea what's going on?\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/c2071\">#c2071\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[1997],{"name":1985,"color":1986},2385,"Latest Vue version update crashes my nuxt app","2023-01-18T15:55:11Z","https://github.com/nuxt/nuxt/issues/2385",0.62187874,{"labels":2004,"number":2009,"owner":1988,"repository":1988,"state":1989,"title":2010,"updated_at":2011,"url":2012,"score":2013},[2005,2008],{"name":2006,"color":2007},"pending triage","E99695",{"name":1985,"color":1986},6163,"Server side 'only' component shows error in development mode","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6163",0.63826454,{"labels":2015,"number":2018,"owner":1988,"repository":1988,"state":1989,"title":2019,"updated_at":2020,"url":2021,"score":2022},[2016,2017],{"name":2006,"color":2007},{"name":1985,"color":1986},10479," ERROR Cannot redefine property: styles","2023-01-22T15:48:28Z","https://github.com/nuxt/nuxt/issues/10479",0.6464469,{"labels":2024,"number":2034,"owner":1988,"repository":1988,"state":1989,"title":2035,"updated_at":2036,"url":2037,"score":2038},[2025,2028,2031],{"name":2026,"color":2027},"enhancement","8DEF37",{"name":2029,"color":2030},"3.x","29bc7f",{"name":2032,"color":2033},"dx","C39D69",14045,"Errors in terminal make it difficult to pinpoint issues","2023-01-19T17:32:46Z","https://github.com/nuxt/nuxt/issues/14045",0.64660907,{"description":2040,"labels":2041,"number":2044,"owner":1988,"repository":1988,"state":1989,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### Version\n\n[edge](https://github.com/nuxt.js/releases/tag/edge)\n\n### Reproduction link\n\n[https://github.com/imow-frontend/imow/tree/feat-nuxt%40edge](https://github.com/imow-frontend/imow/tree/feat-nuxt%40edge)\n\n### Steps to reproduce\n\nRunning nuxt@edge on Node 8.9.4 and Yarn 1.5.1:\n\n1: run `yarn dev` to start the development server which builds on express .everything compiles susses. the Server listening on http://127.0.0.1:3000.\n2: get the http://127.0.0.1:3000 you'll see the following error.\n\n```\n× error Error: Module build failed (from ./node_modules/vue-loader/index.js):\n TypeError: Cannot read property 'vue' of undefined\n at Object.module.exports (C:\\code\\imow\\node_modules\\vue-loader\\lib\\loader.js:61:18)\n at Object../.nuxt/components/nuxt-error.vue (server-bundle.js:372:7)\n at __webpack_require__ (webpack/bootstrap:25:0)\n at Module../.nuxt/index.js (server-bundle.js:509:84)\n at __webpack_require__ (webpack/bootstrap:25:0)\n at Module../.nuxt/server.js (server-bundle.js:1024:64)\n at __webpack_require__ (webpack/bootstrap:25:0)\n at server-bundle.js:118:18\n at Object.\u003Canonymous> (server-bundle.js:121:10)\n at evaluateModule (C:\\code\\imow\\node_modules\\vue-server-renderer\\build.js:8349:21)\n at C:\\code\\imow\\node_modules\\vue-server-renderer\\build.js:8407:18\n at new Promise (\u003Canonymous>)\n at C:\\code\\imow\\node_modules\\vue-server-renderer\\build.js:8399:14\n at Object.renderToString (C:\\code\\imow\\node_modules\\vue-server-renderer\\build.js:8575:9)\n at Renderer.renderRoute (C:\\code\\imow\\node_modules\\nuxt\\lib\\core\\renderer.js:343:41)\n at Renderer.nuxtMiddleware (C:\\code\\imow\\node_modules\\nuxt\\lib\\core\\middleware\\nuxt.js:13:31)\n at call (C:\\code\\imow\\node_modules\\connect\\index.js:239:7)\n```\n\n\n### What is expected ?\n\nThe server should not throw an error.\n\n### What is actually happening?\n\nCannot read property 'vue' of undefined\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7580\">#c7580\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2042,2043],{"name":2006,"color":2007},{"name":1985,"color":1986},3740,"[edge] Server-side rendering get vue-loader error","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3740",0.6518909,{"description":2050,"labels":2051,"number":2057,"owner":1988,"repository":1988,"state":1989,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Version\n\n[v2.3.4](https://github.com/nuxt.js/releases/tag/v2.3.4)\n\n### Reproduction link\n\n[https://github.com/fy0/nuxttest](https://github.com/fy0/nuxttest)\n\n### Steps to reproduce\n\n1. create an empty project with `create-nuxt-app`\n2. npm i --save axios\n3. write a simple plugin for vue router:\n```javascript\nimport axios from 'axios'\n\nlet theData = null\n\nexport default ({ app }) => {\n app.router.beforeEach(async function (to, from, next) {\n if (!theData) {\n let ret = await axios.get(`http://localhost:8888/`)\n console.log(111, ret)\n theData = ret\n }\n next()\n })\n}\n```\n\n4. start the `backend.py` (requires python 3.6, tornado), `npm run dev` and access localhost:3000\n\n5. get the error \n\n\n\n\n### What is expected ?\n\nNothing happened.\n\n### What is actually happening?\n\n```[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside \u003Cp>, or missing \u003Ctbody>. Bailing hydration and performing full client-side render.```\n\n### Additional comments?\n\nI want fetch some global data before any page loaded.\n\nMaybe it's not the recommend method, but why i got the error? I just sent a request.\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8478\">#c8478\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2052,2055,2056],{"name":2053,"color":2054},"stale","ffffff",{"name":2006,"color":2007},{"name":1985,"color":1986},4765,"Virtual DOM tree not match after a simple request","2023-01-22T15:32:59Z","https://github.com/nuxt/nuxt/issues/4765",0.6532839,{"description":2063,"labels":2064,"number":2067,"owner":1988,"repository":1988,"state":1989,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.0\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-4byrfr?file=modules%2Fcode-block.ts,app.vue\r\n\r\n### Describe the bug\r\n\r\nI have installed a vue component from NPM and created a nuxt module for it:\r\n\r\n```javascript\r\nimport { defineNuxtModule, addComponent } from '@nuxt/kit'\r\n\r\nexport default defineNuxtModule({\r\n setup() {\r\n addComponent({\r\n name: 'VCodeBlock',\r\n export: 'VCodeBlock',\r\n filePath: '@wdns/vue-code-block',\r\n mode: \"client\",\r\n })\r\n },\r\n})\r\n```\r\n\r\nHowever, despite `mode: \"client\"` whenever I put it in a nuxt page, layout or component I still get an ssr related issue\r\n\r\n```\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\nI also have the same error if I just import the component without using nuxt modules \r\nIf I completely disable SSR, it works fine. \r\n\r\nIf I remove mode client, it's worse : it says window is undefined\r\n\r\nI would assume the problem is that the module is client side... but the component use it in isn't, therefore it's rendered before it should. \r\n\r\nIt does feel like a bug however because you'd assume mode client would work. What does `mode:client` do exactly ? \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n```\r\n",[2065,2066],{"name":2029,"color":2030},{"name":2006,"color":2007},24478,"node_modules component in nuxt modules : I still get SSR related errors despite `mode:client`","2023-11-28T23:34:19Z","https://github.com/nuxt/nuxt/issues/24478",0.65366143,{"labels":2073,"number":2079,"owner":1988,"repository":1988,"state":1989,"title":2080,"updated_at":2081,"url":2082,"score":2083},[2074,2075,2076],{"name":2029,"color":2030},{"name":2006,"color":2007},{"name":2077,"color":2078},"needs reproduction","FBCA04",14497,"es modules not working on nuxt 3","2023-01-19T17:36:12Z","https://github.com/nuxt/nuxt/issues/14497",0.6541357,{"labels":2085,"number":2090,"owner":1988,"repository":1988,"state":1989,"title":2091,"updated_at":2092,"url":2093,"score":2094},[2086,2087],{"name":2029,"color":2030},{"name":2088,"color":2089},"bug","d73a4a",12075,"Server Side Rendering Error - Windows OS","2023-01-19T15:54:28Z","https://github.com/nuxt/nuxt/issues/12075",0.6543386,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"rgMqUbUSAlck-6wbEMyDAXVp_sN12muWEh87yb3egEM":-1},"/nuxt/nuxt/3515"]