` has a conditional rendered children using `v-if`, the following error is thrown:\r\n\r\n```shell\r\nTypeError: Cannot read properties of null (reading 'nextSibling')\r\n at nextSibling (framework.w6niQ9Mc.js:17:682)\r\n at kt (framework.w6niQ9Mc.js:13:29640)\r\n at N (framework.w6niQ9Mc.js:13:21176)\r\n at v (framework.w6niQ9Mc.js:13:23760)\r\n at Object.process (framework.w6niQ9Mc.js:13:37355)\r\n at N (framework.w6niQ9Mc.js:13:21489)\r\n at v (framework.w6niQ9Mc.js:13:23760)\r\n at O (framework.w6niQ9Mc.js:13:23130)\r\n at L (framework.w6niQ9Mc.js:13:22048)\r\n at N (framework.w6niQ9Mc.js:13:21426)\r\n```\n\n### Reproduction\n\nMinimal reproduction link: https://stackblitz.com/edit/vitepress-nextsibling-ssr-error\r\n\r\nSee the `TeleportedComponent.vue` and `error-demo.md` files.\r\n\r\n___\r\n\r\n**Reproduction steps**:\r\n\r\n- Create a production build (`npm run docs:build`)\r\n- Serve the production (`npm run docs:dev`)\r\n- Go directly the URL where the custom component is imported\r\n- Interact with the custom component button to trigger the menu\r\n- An error is thrown in the console, the component doesn't work\r\n\r\nNow, this issue can be avoided if the user go to any other page that doesn't contain the component, and go back to this page.\n\n### Expected behavior\n\nThe conditional rendering of the children using a `v-if`, inside the `\u003CTeleport />`, should not cause any issues on the first page load.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.5\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 95.19 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm\r\n pnpm: 8.15.1 - ~/Library/pnpm/pnpm\r\n Browsers:\r\n Brave Browser: 126.1.67.123\r\n Chrome: 126.0.6478.126\r\n Safari: 17.5\r\n npmPackages:\r\n vitepress: 1.2.3 => 1.2.3\n```\n\n\n### Additional context\n\nI've first noticed the issue when working on an open-source [vue3-select-component](https://github.com/TotomInc/vue3-select-component).\r\n\r\nE.g. go to https://vue3-select-component.vercel.app/demo/single-select.html and interact with the component. You'll see the same error thrown in the console.\r\n\r\nFor reference: https://github.com/TotomInc/vue3-select-component/issues/78\n\n### Validations\n\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2952],{"name":2953,"color":2954},"need more info","bdbefc",3987,"SSR issue with Teleport and conditional rendering of its children (Cannot read properties of null (reading 'nextSibling'))","2024-07-04T04:41:55Z","https://github.com/vuejs/vitepress/issues/3987",0.748178,{"description":2961,"labels":2962,"number":2963,"owner":2871,"repository":2872,"state":2908,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Describe the bug\n\nI've implemented a vitepress site for a component library used internally. Running npm run docs:dev works as intended and the documentation site is functional. When I attempt to build the docs site, I get an ambiguous error.\r\n\r\nProject link: https://github.com/MelihAltintas/vue3-openlayers\r\n\r\n```\r\n> vue3-openlayers@0.1.74 docs:build\r\n> vitepress build docs\r\n\r\n\r\n vitepress v1.0.0-alpha.50\r\n\r\n⠦ building client + server bundles...\r\n(!) Some chunks are larger than 500 kBs after minification. Consider:\r\n- Using dynamic import() to code-split the application\r\n- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks\r\n- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.\r\n✓ building client + server bundles...\r\nbuild error:\r\nError [ERR_MODULE_NOT_FOUND]: Cannot find package 's' imported from D:\\vue3-openlayers\\docs\\.vitepress\\.temp\\app.js\r\n at new NodeError (node:internal/errors:371:5)\r\n at packageResolve (node:internal/modules/esm/resolve:884:9)\r\n at moduleResolve (node:internal/modules/esm/resolve:929:18)\r\n at defaultResolve (node:internal/modules/esm/resolve:1044:11)\r\n at ESMLoader.resolve (node:internal/modules/esm/loader:422:30)\r\n at ESMLoader.getModuleJob (node:internal/modules/esm/loader:222:40)\r\n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/module_job:76:40)\r\n at link (node:internal/modules/esm/module_job:75:36)\r\n```\n\n### Reproduction\n\nnpm run docs:build\n\n### Expected behavior\n\nwork like a npm run docs:dev\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz\r\n Memory: 11.31 GB / 31.88 GB\r\n Binaries:\r\n Node: 16.13.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.17 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.3.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 111.0.5563.111\r\n Edge: Spartan (44.19041.1266.0), Chromium (111.0.1661.51)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.50 => 1.0.0-alpha.50\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],2137,"dev works perfect but build not work","2023-04-02T00:04:13Z","https://github.com/vuejs/vitepress/issues/2137",0.7545576,["Reactive",2969],{},["Set"],["ShallowReactive",2972],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4m-DIkQf0nHmDjDurI8yLWQ6_akIFiQJXux13xZN2WU":-1},"/vuejs/vitepress/3160"]