```\r\n\r\nIt doesn't seem to be correct:\r\n\r\n\r\n\r\nHow to make it look correct, just like on the homepage?:\r\n\r\n\r\n\r\n",[3034],{"name":3021,"color":3022},4273,"How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.76863796,{"description":3041,"labels":3042,"number":3044,"owner":3024,"repository":3025,"state":3026,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### Is your feature request related to a problem? Please describe.\n\nMy project spans several repositories under a single GitHub user. I'm building a vitepress project (which is in its own repository) for documentation and API reference for all my repositories because they are all related to each other. I like to include Markdown and code snippets from each of the repositories. \r\n\r\nI've tried this for including files from my vitepress repository, like this\r\n\r\n```markdown\r\n\u003C!--@include: ./setup.md-->\r\n```\r\n\r\nand it works nicely, but \r\n\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/README.md#reporting-issues -->\r\n```\r\n\r\ndoes not work. \r\n\r\nIt would be very helpful to be able to include arbitrary markdown and code into my vitepress project. Is there a way to do this?\n\n### Describe the solution you'd like\n\nIt would be very helpful to be able to include arbitrary markdown and code into my vitepress project. \r\n\r\nSections from a Markdown file:\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/README.md#reporting-issues -->\r\n```\r\n\r\nLines from a JSON (or any source code) file:\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/cves/1999/0xxx/CVE-1999-0001.json{123,131} -->\r\n```\r\n\r\nIs there a way to do this?\n\n### Describe alternatives you've considered\n\nOne possible alternative to doing it in vitepress' markdown extension is to write a Vue component that reads in the file and displays that, but having it as a feature of vitepress so others can use it would be more useful to the vitepress community.\n\n### Additional context\n\nI think this feature would be useful for writing Guides and API References, but also other documentation (e.g., a full tutorial for using Vue and vitepress in a Docker container, in a section for how to set up the development environment) where it would be even more important so that the doc is always up-to-date with its dependent projects.\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.",[3043],{"name":3021,"color":3022},3349,"@include markdown and code files from an arbitrary public URL","2025-03-02T18:10:08Z","https://github.com/vuejs/vitepress/issues/3349",0.77431047,{"description":3050,"labels":3051,"number":3053,"owner":3024,"repository":3025,"state":3026,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Is your feature request related to a problem? Please describe.\n\nI am always frustrated when searching for related content across the site.\n\n### Describe the solution you'd like\n\nIt might be a great idea to have some kind of tag system very much like the way a hashtag works, where you can set the tags in the frontmatter and the vitepress tool would automatically inject those tags at the top of the page or the bottom of the page. These tags would then become searchable via the built-in search tool or you could have a list of tags in the sidebar appear, so when you click on a tag it will display or the related content that is associated to that tag.\n\n### Describe alternatives you've considered\n\nI have not tried any alternatives, I believe that Vitepress does not provide an alternative solution.\n\n### Additional context\n\nI am building a resource for making the law more approachable and accessible to the everyday South African called lawforidiots.org, I have realized that the way that i intend for the content to be laid out would require some kind of tagging system because there will eventually be a lot of content that is related overtime. Therefore, a tagging system would be the best way to go. I see there is another ticket https://github.com/vuejs/vitepress/issues/3029 but I thought I would create a duplicate just for more context on the matter\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.",[3052],{"name":3021,"color":3022},3254,"Searchable tags","2025-03-02T18:10:16Z","https://github.com/vuejs/vitepress/issues/3254",0.77500784,{"description":3059,"labels":3060,"number":3061,"owner":3024,"repository":3025,"state":3062,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Is your feature request related to a problem? Please describe.\n\n当我点击第一个 `code-group` 中的 `模式二` 之后,第二个 `code-group` 中并未切换到 `模式二`。\r\n\r\n\r\n\n\n### Describe the solution you'd like\n\n当我点击第一个 `code-group` 中的 `模式二` 之后,第二个 `code-group` 中也会切换到 `模式二`。\r\n\r\n\r\n\n\n### Describe alternatives you've considered\n\nLike this:https://docs.livekit.io/realtime/server/generating-tokens/\r\n\r\n\r\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] 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.",[],3205,"closed","code-group 支持统一切换","2023-11-22T00:04:34Z","https://github.com/vuejs/vitepress/issues/3205",0.68804497,{"description":3068,"labels":3069,"number":3070,"owner":3024,"repository":3025,"state":3062,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Describe the bug\n\nVitePress ignores the `vite.clearScreen: false` option - running `vitepress build` will clear the screen regardless.\r\n\r\nThis is causing issues in our turbo build monorepo - when building several packages at once, VitePress's clear screen clears the log output for packages that were built before it.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-dtu41vnr?file=package.json\r\n\r\n1. Install dependencies\r\n2. Run `npx vitepress build docs`\r\n3. See that screen is cleared, despite vite.clearScreen:false in docs/.vitepress/config.ts\n\n### Expected behavior\n\nScreen should not be cleared if vite.clearScreen:false is set\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 15.2\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 78.41 MB / 32.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 22.12.0 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/node\r\n Yarn: 1.22.19 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/yarn\r\n npm: 10.9.0 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/npm\r\n Browsers:\r\n Chrome: 131.0.6778.205\r\n Safari: 18.2\r\n npmPackages:\r\n vitepress: 1.5.0 => 1.5.0\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.",[],4468,"`vite.clearScreen: false` option is ignorred","2025-01-14T04:42:24Z","https://github.com/vuejs/vitepress/issues/4468",0.7482143,{"description":3076,"labels":3077,"number":3081,"owner":3024,"repository":3025,"state":3062,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Describe the bug\n\nI want to use VitePress to generate some static HTML pages, and I hope these HTML files can be opened directly with a browser by double-clicking, without the need for a web server. But after run `npm run docs:build`, and open the HTML file in Chrome, there came an error in Network panel, `Name: inter-roman-latin.bvIUbFQP.woff2`, `Status: (failed)net::ERR_FILE_NOT_FOUND`.\r\n\r\n\r\nIn `.vitepress/dist/assets/style.SZl3QJfs.css`, you can see the url of file `inter-roman-latin.bvIUbFQP.woff2` is `/assets/inter-roman-latin.bvIUbFQP.woff2` but not `./assets/inter-roman-latin.bvIUbFQP.woff2`. This might be the cause of the error.\r\n\r\n\r\n\n\n### Reproduction\n\nRun the command:\r\n\r\n```\r\nnpm install --save-dev vitepress\r\n\r\nnpx vitepress init\r\n\r\n Where should VitePress initialize the config?\r\n ./\r\n\r\n Site title:\r\n My Awesome Project\r\n\r\n Site description:\r\n A VitePress Site\r\n\r\n Theme:\r\n Default Theme (Out of the box, good-looking docs)\r\n\r\n Use TypeScript for config and theme files?\r\n No\r\n\r\n Add VitePress npm scripts to package.json?\r\n Yes\r\n```\r\n\r\nEdit `.vitepress/config.mjs`, add `base : '.'` and `mpa : true`:\r\n\r\n```\r\nimport { defineConfig } from 'vitepress'\r\n\r\n// https://vitepress.dev/reference/site-config\r\nexport default defineConfig({\r\n title: \"My Awesome Project\",\r\n description: \"A VitePress Site\",\r\n themeConfig: {\r\n // https://vitepress.dev/reference/default-theme-config\r\n nav: [\r\n { text: 'Home', link: '/' },\r\n { text: 'Examples', link: '/markdown-examples' }\r\n ],\r\n\r\n sidebar: [\r\n {\r\n text: 'Examples',\r\n items: [\r\n { text: 'Markdown Examples', link: '/markdown-examples' },\r\n { text: 'Runtime API Examples', link: '/api-examples' }\r\n ]\r\n }\r\n ],\r\n\r\n socialLinks: [\r\n { icon: 'github', link: 'https://github.com/vuejs/vitepress' }\r\n ]\r\n },\r\n base : '.',\r\n mpa : true\r\n})\r\n```\r\n\r\nAnd build the docs:\r\n\r\n```\r\nnpm run docs:build\r\n```\r\n\r\nOpen the file `.vitepress/dist/api-examples.html` in Chrome by double-clicking, and then open the Network panel of Chrome's DevTools to see the error.\n\n### Expected behavior\n\nAfter set `base : '.'` in `config.mjs`, the url of assets should start with `./assets/`, but not `/assets/`.\r\n\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)\r\n CPU: (4) x64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz\r\n Memory: 10.44 GB / 15.52 GB\r\n Container: Yes\r\n Shell: 3.6.0 - /usr/bin/fish\r\n Binaries:\r\n Node: 18.17.1 - ~/dev/nodejs/nodejs/bin/node\r\n npm: 10.4.0 - ~/dev/nodejs/nodejs/bin/npm\r\n Browsers:\r\n Chrome: 112.0.5615.165\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.42 => 1.0.0-rc.42\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.",[3078],{"name":3079,"color":3080},"wont fix","EDEED1",3563,"The link in css file is not correct after setting base to '.' in config.mjs","2024-02-16T00:04:27Z","https://github.com/vuejs/vitepress/issues/3563",0.75015926,{"description":3087,"labels":3088,"number":3095,"owner":3024,"repository":3025,"state":3062,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Describe the bug\n\nHTML entities not decoded , for instance \r\n`\"إدارة أوامر للمعدات والمخزون\",`\n\n### Reproduction\n\nCurrent template\r\n\r\n`\u003Cslot name=\"home-hero-info\">\r\n \u003Ch1 v-if=\"name\" class=\"name\">\r\n \u003Cspan class=\"clip\">{{ name }}\u003C/span>\r\n \u003C/h1>\r\n \u003Cp v-if=\"text\" class=\"text\">{{ text }}\u003C/p>\r\n \u003Cp v-if=\"tagline\" class=\"tagline\">{{ tagline }}\u003C/p>\r\n \u003C/slot>`\n\n### Expected behavior\n\nProposed template\r\n`\u003Cslot name=\"home-hero-info\">\r\n \u003Ch1 v-if=\"name\" class=\"name\">\r\n \u003Cspan class=\"clip\" v-html=\"name\">\u003C/span>\r\n \u003C/h1>\r\n \u003Cp v-if=\"text\" class=\"text\" v-html=\"text\">\u003C/p>\r\n \u003Cp v-if=\"tagline\" class=\"tagline\" v-html=\"tagline\">\u003C/p>\r\n \u003C/slot>`\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.22000\r\n CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz\r\n Memory: 4.09 GB / 15.88 GB\r\n Binaries:\r\n Node: 18.15.0 - D:\\Tools\\Nodejs\\18.15.0\\node.EXE\r\n npm: 9.6.2 - D:\\Tools\\Nodejs\\18.15.0\\npm.CMD\r\n pnpm: 8.6.3 - D:\\Tools\\Nodejs\\18.15.0\\pnpm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22000.120.0), Chromium (114.0.1823.82)\r\n Internet Explorer: 11.0.22000.120\r\n npmPackages:\r\n vitepress: 1.0.0-beta.5 => 1.0.0-beta.5\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.",[3089,3092],{"name":3090,"color":3091},"theme","0754FB",{"name":3093,"color":3094},"contribution welcome","11E4B8",2621,"[Default theme] VPHero html entities not decoded ","2023-07-25T00:04:49Z","https://github.com/vuejs/vitepress/issues/2621",0.766699,{"description":3101,"labels":3102,"number":3106,"owner":3024,"repository":3025,"state":3062,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Describe the bug\n\nThe external link in siderbar seems not work.\r\n\r\nWhen I click the MarkdownCanDo button, the website jumps to `https://www.gantrol.com/en/software/https:/www.markdowncando.com/` instead of `https://www.markdowncando.com/`\r\n\r\n\r\n\n\n### Reproduction\n\nI write [a blog website](https://www.gantrol.com/en/CS/examples) with vitepress ([github](https://github.com/gantrol/gantrol-blog))\r\n\n\n### Expected behavior\n\nHere is a PR that describes the feature, https://github.com/vuejs/vitepress/pull/1881\n\n### System Info\n\n```Text\n\"vitepress\": \"1.0.0-rc.45\"\r\n\r\n[config file](https://github.com/gantrol/gantrol-blog/blob/main/.vitepress/config/en.ts)\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.",[3103],{"name":3104,"color":3105},"bug: pending triage","e99695",3656,"Can sidebar has external links?","2024-03-22T00:04:26Z","https://github.com/vuejs/vitepress/issues/3656",0.7699153,{"description":3112,"labels":3113,"number":3114,"owner":3024,"repository":3025,"state":3062,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Describe the bug\n\nClick on the search box and the page will look right offset,This problem also exists in Vue,This is caused by the scroll bar on the right。\n\n### Reproduction\n\nClick on the search box.\n\n### Expected behavior\n\nClick the search box, the page does not offset\n\n### System Info\n\n```Text\nall\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.",[],3589,"searchbox","2024-03-24T00:05:34Z","https://github.com/vuejs/vitepress/issues/3589",0.77185047,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fMFlJN_fJ6TJ64dkG8FACqmTRD9zF8f1axFMgHrmSa0s":-1},"/vuejs/vitepress/3613"]