\r\n}\r\n\r\nexport default Component;\r\n```\r\n\r\n// Import this code in \r\n```vue\r\n\u003Cdiv ref=\"el\" />\r\n\r\n\u003Cscript setup>\r\nimport { createElement } from 'react'\r\nimport { createRoot } from 'react-dom/client'\r\nimport { ref, onMounted } from 'vue'\r\nimport Simple from '../components/simple/Simple.jsx'\r\n\r\nconst el = ref()\r\nonMounted(() => {\r\n const root = createRoot(el.value)\r\n root.render(createElement(Simple, {}, null))\r\n})\r\n\u003C/script>\r\n```\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nThe project should build... It works fine in dev mode...\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: macOS 12.5\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 1.16 GB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.20.1 - ~/.nvm/versions/node/v16.20.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v16.20.1/bin/yarn\r\n npm: 8.19.4 - ~/.nvm/versions/node/v16.20.1/bin/npm\r\n Browsers:\r\n Chrome: 115.0.5790.114\r\n Safari: 15.6\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2903],{"name":2904,"color":2905},"bug: pending triage","e99695",2709,"Unable to build the docs project when importing a module from node_modules","2023-08-07T00:04:27Z","https://github.com/vuejs/vitepress/issues/2709",0.7277145,{"description":2912,"labels":2913,"number":2915,"owner":2869,"repository":2870,"state":2895,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Is your feature request related to a problem? Please describe.\n\nVitepress breaks build if links to localhost are found reporting errors like \r\n\r\n> Found dead link http://localhost:65200\r\n\r\nIf you want to use links to localhost you have to choose a workaround:\r\n- set `config.ignoreDeadLinks: true`\r\n- change links to ip address instead, like `http://127.0.0.1:65200`\r\n- use html anchor instead\r\n\r\nThose options work, but have some problems of their own:\r\n- `config.ignoreDeadLinks` forces you to check for dead links manually, which is problematic if you have many of them\r\n- links to `127.0.0.1` are much less readable and user friendly than `localhost`\r\n- html anchor is just mess in your documents. It goes against the main purpose of using markdown in the first place\r\n\r\nI agree that in most cases you don't have to deal with localhost links that often. There are, however, cases when you might have many of such links. For example I am currently describing a system that uses many localhost links as a target for reverse proxy configuration. I don't want to use any of above workarounds.\r\n\n\n### Describe the solution you'd like\n\nPlease add option to configuration to allow links on localhost.\r\n\r\nIt might look like below:\r\n```json\r\nlocalhostLinks: 'reportAsDead' | 'check' | 'allow' \r\n```\r\n- default value should be `reportAsDead` for backward compatibility\r\n- `check` should check the link as it does with all non localhost links\r\n- `allow` should treat localhost links as valid, without trying to access them. It might be useful for situations when you build documentation on machine without access to all those localhost links\r\n\n\n### Describe alternatives you've considered\n\n- set `config.ignoreDeadLinks: true`\r\n- change links to ip address instead, like `http://127.0.0.1:65200`\r\n- use html anchor instead\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.vuejs.org).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2914],{"name":2880,"color":2881},1712,"reporting localhost as dead link should be configurable","2023-01-28T00:04:02Z","https://github.com/vuejs/vitepress/issues/1712",0.72944474,{"description":2921,"labels":2922,"number":2924,"owner":2869,"repository":2870,"state":2895,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Describe the bug\r\n\r\nIf docs contain a custom element (web component), the `npm run docs:build` command throws error:\r\n\r\n```sh\r\n> test-docs@1.0.0 docs:build\r\n> vitepress build docs\r\n\r\n vitepress v1.0.0-alpha.75\r\n\r\n✓ building client + server bundles...\r\n✖ rendering pages...\r\nbuild error:\r\nReferenceError: customElements is not defined\r\n at T (file:///C:/test/test-docs/docs/.vitepress/.temp/app.js:4297:3)\r\n at Object.enhanceApp (file:///C:/test/test-docs/docs/.vitepress/.temp/app.js:4307:5)\r\n at createApp (file:///C:/test/test-docs/docs/.vitepress/.temp/app.js:4576:17)\r\n at render (file:///C:/test/test-docs/docs/.vitepress/.temp/app.js:4616:33)\r\n at renderPage (file:///C:/test/test-docs/node_modules/vitepress/dist/node/serve-998e6cdd.js:41231:25)\r\n at file:///C:/test/test-docs/node_modules/vitepress/dist/node/serve-998e6cdd.js:41768:21\r\n at Array.map (\u003Canonymous>)\r\n at build (file:///C:/test/test-docs/node_modules/vitepress/dist/node/serve-998e6cdd.js:41767:94)\r\n```\r\n\r\n### Reproduction\r\n\r\n1. Create a custom element `TestComponent.ce.vue` with Vue 3.2 `defineCustomElement` function.\r\n2. Define the component in its `index.js` file\r\n\r\n```\r\nimport { defineCustomElement } from \"vue\";\r\nimport TestComponent from './TestComponent.ce.vue'\r\n\r\nconst TestComponentCE = defineCustomElement(TestComponent)\r\n\r\nexport function defineTestComponentCE() {\r\n if (!customElements.get('test-component')) {\r\n customElements.define('test-component', TestComponentCE);\r\n }\r\n}\r\n\r\nexport { TestComponentCE }\r\n```\r\n\r\n3. Use the custom element on a Vitepress page\r\n\r\n`docs/.vitepress/theme/index.ts`\r\n```js\r\n// https://vitepress.dev/guide/custom-theme\r\nimport { h } from 'vue'\r\nimport Theme from 'vitepress/theme'\r\nimport './style.css'x\r\nimport {defineTestComponentCE} from 'test-ui';\r\n\r\nexport default {\r\n ...Theme,\r\n Layout: () => {\r\n return h(Theme.Layout, null, {\r\n // https://vitepress.dev/guide/extending-default-theme#layout-slots\r\n })\r\n },\r\n enhanceApp({ app, router, siteData }) {\r\n defineTestComponentCE()\r\n }\r\n}\r\n```\r\n\r\n`some md page`\r\n```\r\n\u003Ctest-component>\u003C/test-component>\r\n```\r\n\r\n### Expected behavior\r\n\r\nCustom elements to work in Vitepress\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n Binaries:\r\n Node: 18.12.1 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 8.19.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.75 => 1.0.0-alpha.75\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2923],{"name":2904,"color":2905},2367,"Vitepress cannot build custom elements (web components)","2023-06-14T00:04:15Z","https://github.com/vuejs/vitepress/issues/2367",0.72991055,{"description":2930,"labels":2931,"number":2938,"owner":2869,"repository":2870,"state":2895,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Describe the bug\n\nWhen sidebar is not present, the page is not scrolled and outline is scrolled down, it overflows the navbar.\r\n\r\n \r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-v81ufa\r\n\r\n1. Make sure width is high enough so that outline is shown\r\n2. Without scrolling the main page content hover over the outline and scroll down\r\n3. Observe that the outline overflows the navbar\n\n### Expected behavior\n\nOutline is clipped when over navbar in the same way when sidebar is present.\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz\r\n Memory: 45.66 GB / 63.92 GB\r\n Binaries:\r\n Node: 18.2.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.5 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 9.6.6 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.1\n```\n\n\n### Additional context\n\n_No response_\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.",[2932,2935],{"name":2933,"color":2934},"theme","0754FB",{"name":2936,"color":2937},"contribution welcome","11E4B8",2442,"Outline overflows navbar when sidebar not present","2023-08-16T00:04:22Z","https://github.com/vuejs/vitepress/issues/2442",0.74931806,{"description":2944,"labels":2945,"number":2947,"owner":2869,"repository":2870,"state":2895,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\n\u003Cimg width=\"559\" alt=\"image\" src=\"https://user-images.githubusercontent.com/50388827/231996524-3bb1a93b-8a74-492f-a6d3-ca1e9e880e01.png\">\r\n\u003Cimg width=\"469\" alt=\"image\" src=\"https://user-images.githubusercontent.com/50388827/231997075-305a330e-34d2-473b-a67f-f438580ff1d8.png\">\r\n\n\n### Reproduction\n\nhttps://www.npmjs.com/package/vitepress?activeTab=code\n\n### Expected behavior\n\nfix dependence-missing problem\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 13.3.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 705.63 MB / 32.00 GB\r\n Shell: 3.2.57 - /bin/sh\r\n Binaries:\r\n Node: 18.14.2 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.5.0 - /usr/local/bin/npm\r\n Browsers:\r\n Safari: 16.4\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.65 => 1.0.0-alpha.65\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.",[2946],{"name":2904,"color":2905},2215,"npm pkg has no `localSearch` option & dependence `minisearch ` about localSearch","2023-04-22T00:04:16Z","https://github.com/vuejs/vitepress/issues/2215",0.75286233,{"description":2953,"labels":2954,"number":2955,"owner":2869,"repository":2870,"state":2895,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Is your feature request related to a problem? Please describe.\n\nI want to vitepress cli support this feature to set some path for vitepress configuration. I search the vitepress docs and found nothing about it.\r\nHonestly, path \"./vitepress/config.ts\" is ugly to me.\n\n### Describe the solution you'd like\n\nLike that: vitepress --config yourConfigPath dev\n\n### Describe alternatives you've considered\n\n_No response_\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] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],2084,"How can I change default config path, like /projectRoot/config/vitepress.config.ts.","2023-03-22T00:03:23Z","https://github.com/vuejs/vitepress/issues/2084",0.7539332,{"description":2961,"labels":2962,"number":2964,"owner":2869,"repository":2870,"state":2895,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\n\nHello, \r\n\r\nI want to add vite.config.js because i have to add entry to my server allow list\r\n\r\n\u003Cimg width=\"1245\" alt=\"Capture d’écran 2022-09-27 à 14 20 52\" src=\"https://user-images.githubusercontent.com/41836255/192524958-f2f2189c-47ef-40ae-a817-dd95c1b8de8b.png\">\r\n\r\nBut It seem not to be use by vitepress. Maybe i did something wrong.\r\n\r\nThanks by advance\n\n### Reproduction\n\n- Create new vitepress project\r\n- Add vite.config.js at the root of the project\r\n- Add some specific configuration\r\n\r\n```js\r\nimport { defineConfig } from 'vite'\r\nexport default defineConfig({\r\n server: {\r\n port: 3030\r\n }\r\n})\r\n\r\n```\r\n\r\n- restart.\n\n### Expected behavior\n\nShould use the new port to serve app\n\n### System Info\n\n```shell\nUse the default config instead of custom\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2963],{"name":2892,"color":2893},1406,"Add vite.conf.js to overloading config","2023-01-21T14:25:16Z","https://github.com/vuejs/vitepress/issues/1406",0.7559536,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fo1_j_61-A7yDYCksTprJfqrwjTmMLEoZcKZPK1Mkrbw":-1},"/vuejs/vitepress/2312"]