```\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",[2865],{"name":2866,"color":2867},"stale","ededed",4273,"vuejs","vitepress","open","How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.72793657,{"description":2877,"labels":2878,"number":2883,"owner":2869,"repository":2870,"state":2871,"title":2884,"updated_at":2885,"url":2886,"score":2887},"### Is your feature request related to a problem? Please describe.\n\nIn the monorepo development mode, sometimes the rendering in docs depends on the code in another repository, so when the code in another repository changes, it is expected to trigger a hot reload of docs\n\n### Describe the solution you'd like\n\nSupport configuration to watch specified folders to trigger hot reload\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.",[2879,2882],{"name":2880,"color":2881},"need more info","bdbefc",{"name":2866,"color":2867},4221,"Support hot reload by watching files not under docs","2024-12-03T17:27:50Z","https://github.com/vuejs/vitepress/issues/4221",0.741543,{"description":2889,"labels":2890,"number":2892,"owner":2869,"repository":2870,"state":2871,"title":2893,"updated_at":2894,"url":2895,"score":2896},"### Is your feature request related to a problem? Please describe.\n\nI am using obsidian ,hidden files and dir , this application in no found\n\n### Describe the solution you'd like\n\nCan I rename this dir .vitepress ? \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.",[2891],{"name":2866,"color":2867},3793,".vitepress dir Whether you can rename it ? ","2024-06-23T07:11:50Z","https://github.com/vuejs/vitepress/issues/3793",0.7587423,{"description":2898,"labels":2899,"number":2903,"owner":2869,"repository":2870,"state":2904,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Describe the bug\r\n\r\nComponents at the start of a line/paragraph don't render their contents as Markdown despite other Markdown renders doing so.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-jgrywo?file=docs%2Findex.md\r\n\r\nLook at \"Some Markdown\" line. I expected it to render as Markdown...\r\n\r\n### Expected behavior\r\n\r\nIt should render as Markdown. When rendered by other systems at least it does. e.g. VS Code Markdown preview.\r\n\r\n### System Info\r\n\r\n```Text\r\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\n Binaries:\r\n Node: 18.20.3 - /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.6 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: latest => 1.2.3\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nVitePress:\r\n\r\n\r\nVS Code:\r\n\r\n\r\n\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.",[2900],{"name":2901,"color":2902},"wont fix","EDEED1",4017,"closed","Components at the start of a line/paragraph don't render their contents as Markdown","2024-07-11T04:42:20Z","https://github.com/vuejs/vitepress/issues/4017",0.68261397,{"description":2910,"labels":2911,"number":2915,"owner":2869,"repository":2870,"state":2904,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Describe the bug\r\n\r\nStep 1\r\n\r\n```vue\r\n\u003Cscript lang=\"jsx\">\r\nimport { CustomLink } from 'my-lib/dist/customLink';\r\nimport { defineComponent } from \"vue\";\r\nexport default defineComponent({\r\n render() {\r\n return (\r\n \u003CCustomLink />\r\n );\r\n },\r\n});\r\n\r\n\u003C/script>\r\n```\r\n\r\nStep 2\r\n\r\nPage md\r\n```\r\n\u003CTest />\r\n\u003Cscript setup>\r\n import Test from '../components/Test.vue'\r\n\u003C/script>\r\n\r\n````\r\n\r\n\r\nResult\r\n\r\n\r\n\r\nBut\r\n\r\nI change for example\r\n\r\n```vue\r\n\r\n\u003Cscript lang=\"jsx\">\r\nimport { defineComponent } from \"vue\";\r\nexport default defineComponent({\r\n render() {\r\n return (\r\n \u003Cdiv>\r\n Hello World :defineConfig\r\n \u003C/div>\r\n );\r\n },\r\n});\r\n\r\n\u003C/script>\r\n\r\n```\r\n\r\nworks\r\n\r\n\r\n\r\nHELP PLEASE\r\n\r\n### Reproduction\r\n\r\nno\r\n\r\n### Expected behavior\r\n\r\nI would expect the component to be seen\r\n\r\n### System Info\r\n\r\n```sh\r\n$ npx envinfo --system --npmPackages vitepress --binaries --browsers\r\nnpx: installed 1 in 2.22s\r\n\r\n System:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz \r\n Memory: 5.52 GB / 15.82 GB\r\n Binaries:\r\n Node: 14.19.0 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.17 - D:\\nodejs\\yarn.CMD\r\n npm: 6.14.16 - D:\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.1\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI want to document my component library in react with vitepress; It might sound crazy but I had a leap of faith says Toretto hehe\r\n\r\nVite config\r\n```ts\r\nimport { defineConfig } from \"vite\";\r\nimport vueJsx from \"@vitejs/plugin-vue-jsx\";\r\nexport default defineConfig({\r\n plugins: [\r\n vueJsx(),\r\n ],\r\n});\r\n\r\n```\r\n\r\n@antfu do you know jeje?\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.",[2912],{"name":2913,"color":2914},"bug: pending triage","e99695",2427,"I try to render React component from library with @vitejs/plugin-vue-jsx and failed. But i render simple div works :(","2023-06-07T00:04:34Z","https://github.com/vuejs/vitepress/issues/2427",0.6883485,{"description":2921,"labels":2922,"number":2924,"owner":2869,"repository":2870,"state":2904,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Describe the bug\n\n```import { createContentLoader } from 'vitepress'\r\ninterface Post{\r\n title: string\r\n date: Date\r\n cover: string | undefined\r\n description: string | undefined\r\n tags: string[] | undefined\r\n categorie: string | undefined\r\n url:string\r\n author: string | undefined\r\n}\r\n\r\ndeclare const data: Post[]\r\nexport { data }\r\nexport default createContentLoader(['**/*.md','!**/index.md','!nav.md','!archives.md','!posts.md'], {\r\n includeSrc: false, \r\n render: false,\r\n excerpt: false,\r\n transform(raw): Post[] {\r\n console.log(\"row\",raw);\r\n return raw\r\n .map(({url, frontmatter }) => ({\r\n title: frontmatter.title,\r\n cover:frontmatter.cover,\r\n description:frontmatter.description,\r\n tags:frontmatter.tags,\r\n categorie:frontmatter.categorie,\r\n date: frontmatter.date,\r\n url: url,\r\n author: frontmatter.author\r\n }))\r\n }\r\n})\r\n```\r\nIn the above code, I utilize createContentLoader to retrieve information from all *.md files; however, I do not require data from index.md or nav.md files located in any directory. I have employed glob patterns for this purpose, but they seem not to be taking effect. How should I address this issue?\n\n### Reproduction\n\ndocs\r\n | ---index.md\r\n | ---foo.md\r\n | --- vue\r\n | --- index.md\r\n | --- foo2.md\n\n### Expected behavior\n\ndocs\r\n | ---foo.md\r\n | --- vue\r\n | --- foo2.md\n\n### System Info\n\n```Text\nvitepress-version: 1.0.2\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.",[2923],{"name":2913,"color":2914},3821,"Watch is not effectively utilizing glob patterns","2024-05-15T04:41:47Z","https://github.com/vuejs/vitepress/issues/3821",0.6970257,{"description":2930,"labels":2931,"number":2933,"owner":2869,"repository":2870,"state":2904,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Describe the bug\n\nI installed Vitepress, built then ran it locally following the documentation of Vercel and everything seemed fine. But when I deployed it to my personal Vercel, my site keeps loading the 404.html. When I visit the Output of Vercel, I couldn't find any index.html and only 404.html. \r\n\r\nHere is currently [the blog of mine](https://vitepress-doc-kappa.vercel.app/) that I deployed to Vercel.\r\n\r\nThis is my current source on Vercel:\r\n\r\n\r\nThis is my current output on Vercel:\r\n\r\n\r\n\n\n### Reproduction\n\nNot sure if this is the correct way to reproduce, but I'll list down the commands that I ran, from install command to deploy:\r\n\r\n```bash\r\nnpm add -D vitepress\r\nnpx vitepress init ./\r\nnpm run docs:build\r\nnpm run docs:preview\r\nvercel --prod\r\n```\n\n### Expected behavior\n\nPage should load index.html when visiting `/`.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19043\r\n CPU: (4) x64 Intel(R) Pentium(R) CPU G4560 @ 3.50GHz\r\n Memory: 2.27 GB / 7.96 GB\r\n Binaries:\r\n Node: 20.0.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.6.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.133)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.39 => 1.0.0-rc.39\n```\n\n\n### Additional context\n\nI use a fresh setup of Vitepress and deploy to a Vercel setting using Node v20.x (which as mentioned on Vercel that is still in Beta). However I did try Node v18.x on Vercel and the error is the same. \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],{"name":2913,"color":2914},3460,"Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.7415435,{"description":2939,"labels":2940,"number":2942,"owner":2869,"repository":2870,"state":2904,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### 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.",[2941],{"name":2913,"color":2914},3656,"Can sidebar has external links?","2024-03-22T00:04:26Z","https://github.com/vuejs/vitepress/issues/3656",0.74476427,{"description":2948,"labels":2949,"number":2953,"owner":2869,"repository":2870,"state":2904,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Is your feature request related to a problem? Please describe.\r\n\r\nConveniently use content-adaptive layout in components on the home page\r\n\r\n### Describe the solution you'd like\r\n\r\n`.vitepress/theme/index.ts`:\r\n```ts\r\nimport HomePage from './component/HomePage'\r\n\r\nexport default {\r\n Layout: () => {\r\n return h(Theme.Layout, null, {\r\n 'home-features-after': () => h(HomePage),\r\n })\r\n },\r\n```\r\n\r\n---\r\n\r\n`HomePage.vue`:\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport{ VPHomeContent } from 'vitepress/theme'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n\t\u003CVPHomeContent>\r\n\t\t\u003C!-- my custom content -->\r\n\t\u003C/VPHomeContent>\r\n\u003C/template>\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\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] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2950],{"name":2951,"color":2952},"contribution welcome","11E4B8",3954,"[New feature] export `VPHomeContent` to provide content-adaptive layout","2024-06-22T04:41:46Z","https://github.com/vuejs/vitepress/issues/3954",0.7480557,{"description":2959,"labels":2960,"number":2964,"owner":2869,"repository":2870,"state":2904,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\r\n\r\nFail to install with yarn in windows, if the folder is not in C drive\r\n\r\n### Reproduction\r\n\r\nOn a folder is not in C drive:\r\n\r\n```sh\r\nyarn init\r\nyarn add -D vitepress vue\r\nyarn vitepress init\r\nyarn run docs:dev\r\n```\r\n\r\nGet this error\r\n\r\n```\r\n vitepress v1.3.1\r\n\r\n ➜ Local: http://localhost:5173/\r\n ➜ Network: use --host to expose\r\n ➜ press h to show help\r\n✘ [ERROR] Could not read from file: E:/Data/note-vitepress/.yarn/__virtual__/vue-virtual-80b135f193/4/C:/Users/User/AppData/Local/Yarn/Berry/cache/vue-npm-3.4.34-9d9c80aee1-10c0.zip/node_modules/vue/dist/vue.runtime.esm-bundler.js\r\n\r\n✘ [ERROR] Could not read from file: E:\\Data\\note-vitepress\\.yarn\\__virtual__\\vitepress-virtual-046653f2bc\\4\\C:\\Users\\User\\AppData\\Local\\Yarn\\Berry\\cache\\vitepress-npm-1.3.1-f5fb335031-10c0.zip\\node_modules\\vitepress\\lib\\vue-demi.mjs\r\n\r\n C:/Users/User/AppData/Local/Yarn/Berry/cache/@vueuse-core-npm-10.11.0-fb26847db9-10c0.zip/node_modules/@vueuse/core/index.mjs:3:320:\r\n 3 │ ...xtTick, reactive, markRaw, unref, getCurrentScope, set, del, isReadonly, onBeforeUpdate } from 'vue-demi';\r\n ╵ ~~~~~~~~~~\r\n```\r\n\r\n\r\n### Expected behavior\r\n\r\nNo issue\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (4) x64 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz\r\n Memory: 1.03 GB / 7.92 GB\r\n Binaries:\r\n Node: 20.15.0 - ~\\AppData\\Local\\Volta\\tools\\image\\node\\20.15.0\\node.EXE\r\n Yarn: 4.3.1 - ~\\AppData\\Local\\Volta\\tools\\image\\yarn\\4.3.1\\bin\\yarn.CMD\r\n npm: 10.7.0 - ~\\AppData\\Local\\Volta\\tools\\image\\node\\20.15.0\\npm.CMD\r\n bun: 1.1.21 - ~\\.bun\\bin\\bun.EXE\r\n Browsers:\r\n Chrome: 127.0.6533.73\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.19041.4355\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.",[2961],{"name":2962,"color":2963},"upstream","BF29ED",4091,"Fail to install with yarn in windows, if the folder is not in C drive","2024-08-09T04:42:09Z","https://github.com/vuejs/vitepress/issues/4091",0.7493504,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgqeEk0zOQ8sJkbm860rO_GD4Qu6uh9ZqqLRh2yZ-2IM":-1},"/vuejs/vitepress/2480"]