\r\n\u003C/VPTeamPage>\r\n\n\n### Expected behavior\n\nit suppose to change Sponsor word like this but didn't work\r\n\r\n\r\n\r\n\n\n### System Info\n\n```Text\nSystem\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.",[2930],{"name":2931,"color":2932},"need more info","bdbefc",4124,"actionText prop on VPTeamMembers components doesn't works","2024-08-20T04:43:16Z","https://github.com/vuejs/vitepress/issues/4124",0.72334725,{"description":2939,"labels":2940,"number":2942,"owner":2869,"repository":2870,"state":2902,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### 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.",[2941],{"name":2920,"color":2921},2367,"Vitepress cannot build custom elements (web components)","2023-06-14T00:04:15Z","https://github.com/vuejs/vitepress/issues/2367",0.72629607,{"description":2948,"labels":2949,"number":2950,"owner":2869,"repository":2870,"state":2902,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Is your feature request related to a problem? Please describe.\n\nI can't find any solution to lazy load images. If I use markdown, vitepress will render the code to:\r\n``` HTML\r\n\u003Cimg src=\"\" alt=\"\">\r\n```\r\nI think it's better to add loading=\"lazy\" to \u003Cimg> tag. This solution doesn't need any plugin.\n\n### Describe the solution you'd like\n\nAlready said above.\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.",[],3316,"Add loading=\"lazy\" to \u003Cimg> tag to support native lazy load feature of browser.","2024-01-07T00:04:59Z","https://github.com/vuejs/vitepress/issues/3316",0.72724974,{"description":2956,"labels":2957,"number":2958,"owner":2869,"repository":2870,"state":2902,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Describe the bug\n\nwith a config file like this https://github.com/tensorchord/envd-docs/blob/main/docs/.vitepress/config.ts\r\nwhen we change the language of doc it did not naviagative to corresponding URL\n\n### Reproduction\n\neg.\r\nwhen we in this page https://envd.tensorchord.ai/zh/guide/build-envd.html\r\nwe click the button to change the language\r\n\r\nwe expect it naviagte to https://envd.tensorchord.ai/guide/build-envd.html\r\nnot https://envd.tensorchord.ai/guide/getting-started.html\n\n### Expected behavior\n\nnaviagte to corresponding URL\n\n### System Info\n\n```shell\nwin 10 chrome 103\n```\n\n\n### Additional context\n\nI'm not sure whether it been fixed on i18n branch or is there any way I have miss to achive this for now.\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.",[],1253,"[i18n]: always naviageto init page when language change not the corresponding URL","2023-01-25T00:04:21Z","https://github.com/vuejs/vitepress/issues/1253",0.7354595,["Reactive",2964],{},["Set"],["ShallowReactive",2967],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feiVdyvUyRVeK-2ueR-lHq5VK2edNsIu4nuJr4AKXCmM":-1},"/vuejs/vitepress/1775"]