\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.",[2900],{"name":2901,"color":2902},"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.6882447,{"description":2909,"labels":2910,"number":2912,"owner":2869,"repository":2870,"state":2883,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Describe the bug\n\nWhen setting the sidebar text, i want to write a simple script tag in the text, such as 'Compare \u003Cscript> the difference with \u003Cscript async>', however, In real rendering, both tags are converted to tags instead of strings, and cannot be displayed\r\n\r\n\n\n### Reproduction\n\nHere is the location [stackblitz](https://stackblitz.com/edit/vite-hiphbr)\n\n### Expected behavior\n\nI want to render 'This is \u003Cscript> \u003Cstyle>', but it renders 'This is'.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\nBinaries:\r\n Node: 18.18.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 10.2.3 - /usr/local/bin/npm\r\n pnpm: 8.15.3 - /usr/local/bin/pnpm\r\nnpmPackages:\r\n vitepress: latest => 1.0.0-rc.44\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.",[2911],{"name":2880,"color":2881},3627,"bug: when you are configuring sidebar in config.*, the '\u003Cscript>' or '\u003Cstyle>' in text will be parsed directly into a tag instead of a string","2024-03-11T00:04:40Z","https://github.com/vuejs/vitepress/issues/3627",0.6918338,{"description":2918,"labels":2919,"number":2921,"owner":2869,"repository":2870,"state":2883,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Describe the bug\n\nWhen I tried to change the style of the `image` on the homepage, there were some situations where I encountered problems.\r\nunder Path: \r\n> .vitepress\\theme\\styles\\vars.css\r\n```css\r\n@keyframes logo-spin {\r\n from {\r\n transform: rotate(0deg);\r\n }\r\n\r\n to {\r\n transform: rotate(360deg);\r\n }\r\n}\r\n\r\n.image-src {\r\n animation: logo-spin infinite 20s linear;\r\n}\r\n```\n\n### Reproduction\n\nstackblitz : https://stackblitz.com/edit/vite-ib4s68?file=README.md\r\n\r\nrepo and explanation : https://github.com/RSS1102/vite-ib4s68\r\n\r\n\n\n### Expected behavior\n\nOn the mobile end\r\n\r\n\r\nOn the PC end\r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics\r\n Memory: 2.19 GB / 13.86 GB\r\n Binaries:\r\n Node: 18.12.1 - E:\\node\\node.EXE\r\n Yarn: 1.22.19 - E:\\node\\yarn.CMD\r\n npm: 9.4.2 - E:\\node\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.1555.0), Chromium (112.0.1722.39)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.64 => 1.0.0-alpha.64\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.",[2920],{"name":2880,"color":2881},2217,"[hero] : The localization problem of `image bg '","2023-04-22T00:04:15Z","https://github.com/vuejs/vitepress/issues/2217",0.69504535,{"description":2927,"labels":2928,"number":2930,"owner":2869,"repository":2870,"state":2883,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Describe the bug\r\n\r\nI'm currently having one markdown file (`index.md`) within the project root itself (`docs` folder) and uses only one Vue SFC called `SampleCard.vue`. I'm using a custom theme. This works fine. \r\n\r\nBut I want to move my markdown file into `docs/content` folder, so I copied my md files into that folder. \r\n\r\nI then tried setting `srcDir` to `content` following the docs - https://vitepress.dev/guide/routing#source-directory. This doesn't work and the error message I get seems to indicate that my vite aliases gets broken when I use srcDir. \r\n\r\nThanks for looking into this. \r\n\r\n### Reproduction\r\n\r\nHere is my minimal github repo (one `index.md` page using one `SampleCard.vue`) - https://github.com/TechAkayy/my-vitepress-tailwindcss-app\r\n\r\nPlease clone, install, `npm run dev`, works fine. \r\n\r\nThen uncomment the `srcDir` settings in `config.ts`, and save. It gets broken. I tried paths relative to both project root, as well as relative to the `docs` folder. \r\n\r\n\u003Cimg width=\"1106\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/73772701/30fa51cb-8ca4-4720-bd37-624eae000b76\">\r\n\r\nError when using `srcDir`:\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nsrcDir should work when moving the md files into a folder. But it didn't. \r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: macOS 12.6.1\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 1.31 GB / 32.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\n Browsers:\r\n Chrome: 115.0.5790.170\r\n Chrome Canary: 118.0.5953.0\r\n Safari: 15.6.1\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.31 => 1.0.0-rc.31\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.",[2929],{"name":2866,"color":2867},2806,"srcDir not working","2024-02-08T00:04:15Z","https://github.com/vuejs/vitepress/issues/2806",0.69525355,{"description":2936,"labels":2937,"number":2938,"owner":2869,"repository":2870,"state":2883,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Is your feature request related to a problem? Please describe.\n\ni am using component library in VitePress project, i want to change dark mode of component library when mode of VitePress have changed\n\n### Describe the solution you'd like\n\nCan you provide a `onChange` callback of mode button\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.",[],2387,"callback of theme change ?","2023-05-27T00:03:44Z","https://github.com/vuejs/vitepress/issues/2387",0.6985133,{"description":2944,"labels":2945,"number":2953,"owner":2869,"repository":2870,"state":2883,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Is your feature request related to a problem? Please describe.\n\nI am currently writing an API documentation and miss a function to specify http(s) requests and websocket/socket.io connections with all their parameters and responses.\n\n### Describe the solution you'd like\n\nDocument API with following features:\r\na) http(s) requests\r\nDisplay the request method and the request URL. (GET, POST, DELETE... and other methods.) It should also be possible to specify the header and body of the request with a description and the types of the parameters. Furthermore, a display for possible returns should be included which displays the response status and the send json/text/number... .\r\n(In short: specification of the request method to an API URL with the necessary parameters and the return).\r\n\r\nb) websocket / socket.io\r\nA specification of websockets contains namespaces with connection options and events. The individual events should be listed separately. These are listed with the parameters their types and descriptions. In addition, expected return events or no return are specified. Events that the server can send at any time should also be listed separately.\r\n(In short: specification of the connection url with accessable namespaces with their connect-options and a list with all events which the client and the server can send).\r\n\r\nFor both extensions, it is best to have a kind of container that directly specifies the function (GET,POST, WS...) and the URL in the header and displays the parameters and the responses when expanded.\r\nIt should also be possible to copy the URL directly by clicking on it.\r\nIt would also be great to extend the copy functionality in such a way that the parameters can be copied formatted in the programming language used (JS, C, Rust...). If the programmer wishes, he can also specify an implementation of the entire function (also in different languages).\r\n\r\nOptionally, an integration for a direct test request via the documentation can also be built in. This would also require input fields for an API key or Auth token and the required parameters.\n\n### Describe alternatives you've considered\n\nSo far I have used containers to specify the URL in the head and the content in the expandable body.\r\nI have also used the code blocks without format.\n\n### Additional context\n\nAll links below show possible designs and functions as described above.\r\n\r\nhttps://petstore.swagger.io/#/pet/\r\nhttps://redocly.github.io/redoc/#tag/pet\r\nhttps://developers.write.as/docs/api/#introduction\r\nhttps://apidocjs.com/example/\r\nhttps://stoplight.io/demo\r\nhttps://readme.com/\r\n\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.",[2946,2949,2952],{"name":2947,"color":2948},"theme","0754FB",{"name":2950,"color":2951},"wont fix","EDEED1",{"name":2866,"color":2867},2338,"http / ws codeblocks","2023-08-12T00:04:10Z","https://github.com/vuejs/vitepress/issues/2338",0.70160204,{"description":2959,"labels":2960,"number":2961,"owner":2869,"repository":2870,"state":2883,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### 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.70579183,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1xjKln0Gn8BXgBJGLFhSfH4QkBbMIkBjIZ8-Mmm7bZg":-1},"/vuejs/vitepress/412"]