\n\u003Cimg width=\"1890\" height=\"470\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1b63e5fd-3d4d-4c14-8861-271409800222\" />\n\u003Cimg width=\"1420\" height=\"215\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1d036d80-1d0f-445e-a799-9763e9b5580e\" />\n\n\n\n### Reproduction\n\nno\n\n### Expected behavior\n\nCan add public path normally\n\n### System Info\n\n```Text\nwindows11 ,chrome latest\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.",[3198],{"name":3199,"color":3200},"need more info","bdbefc",4886,"Document deployment does not support the base option (public path) of the VitePress configuration.?","2025-08-06T06:36:15Z","https://github.com/vuejs/vitepress/issues/4886",0.69053125,{"description":3207,"labels":3208,"number":3210,"owner":3158,"repository":3159,"state":3160,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Describe the bug\n\nI have `.github/workflows/deploy.yml` set up in my project root as doc instructed. And Github action succeeds. However, when I visit my pages, its not vitepress that I see but regular github pages.\r\n\r\nIs there some settings I have to alter in github repository itself?\n\n### Reproduction\n\n\r\nThis is my app structure \r\n\r\n```\r\n- root\r\n - docs (vitepress)\r\n - theme/index.js\r\n - config.js\r\n - index.md \r\n - src (src for my vue component lib)\r\n - dist (for my vue component lib)\r\n```\r\n\r\nThis is my github workflow deploy.yml\r\n```\r\nname: Deploy\r\n\r\non:\r\n push:\r\n branches:\r\n - master\r\n\r\njobs:\r\n deploy:\r\n runs-on: ubuntu-latest\r\n steps:\r\n - uses: actions/checkout@v2\r\n - uses: actions/setup-node@v3\r\n with:\r\n node-version: 16\r\n cache: npm\r\n - run: npm ci\r\n\r\n - name: Build\r\n run: npm run docs:build\r\n\r\n - name: Deploy\r\n uses: peaceiris/actions-gh-pages@v3\r\n with:\r\n github_token: ${{ secrets.GITHUB_TOKEN }}\r\n publish_dir: docs/.vitepress/dist\r\n```\n\n### Expected behavior\n\nBuilt vitepress in github pages.\n\n### System Info\n\n```shell\n(Local)\r\nSystem:\r\n OS: macOS 12.2\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 99.72 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\n```\n\n\n### Additional context\n\nMy repository is in an organization.\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.",[3209],{"name":3152,"color":3153},1144,"Github pages shows index.md natively","2023-01-21T14:26:58Z","https://github.com/vuejs/vitepress/issues/1144",0.693844,{"description":3216,"labels":3217,"number":3221,"owner":3158,"repository":3159,"state":3160,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Describe the bug\n\nThe latest version of VitePress is not respecting `vite.config.ts` in my project (a very mini one). It's working in the stackblitz template, but my project structures a little bit differently (the `docs` folder is the root) so I'm not sure if it's a bug or it's intended.\r\n\r\nIf someone can please clone and have a look, it's really appreciated.\r\n\r\nAnd also, seems documentation of customizing `Vite`'s configuration is missing in the docs\n\n### Reproduction\n\nhttps://github.com/xsjcTony/docs\r\n\r\nI've put `vite.config.ts` in both root and under `.vitepress` but none of them works.\r\nThanks a lot for the help!\n\n### Expected behavior\n\nIt should pick up either `vite.config.ts` (either at the root or in `.vitepress` folder, I think it should pick the one at the root)\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz\r\n Memory: 42.69 GB / 63.84 GB\r\n Binaries:\r\n Node: 18.14.0 - C:\\NodeJS\\node.EXE\r\n Yarn: 1.22.19 - C:\\NodeJS\\yarn.CMD\r\n npm: 9.4.2 - C:\\NodeJS\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.41)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.46 => 1.0.0-alpha.46\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.",[3218],{"name":3219,"color":3220},"docs","0075ca",1939,"Latest version of VitePress is not respecting `vite.config.ts`","2023-07-27T00:04:23Z","https://github.com/vuejs/vitepress/issues/1939",0.69480604,{"description":3227,"labels":3228,"number":3232,"owner":3158,"repository":3159,"state":3160,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Describe the bug\n\n使用官方文档的部署脚本成功部署到Github Pages之后,此时如果配置使用自定义域名的话,访问时样式会丢失\n\n### Reproduction\n\n1. 博客目录结构如下所示:\u003Cbr />\r\n2. 配置文件如下所示:\u003Cbr /> \n\n### Expected behavior\n\n使用 Github 自带的 https://xihuanxiaorang.github.io/docs/ 访问就没有任何问题,如果是使用自定义域名 https://docs.xiaorang.fun/ 的话,样式就会丢失\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (4) x64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz\r\n Memory: 659.73 MB / 3.92 GB\r\n Binaries:\r\n Node: 20.11.0 - E:\\nodejs\\node.EXE\r\n Yarn: 1.22.21 - E:\\nodejs\\node_global\\yarn.CMD\r\n npm: 10.2.4 - E:\\nodejs\\npm.CMD\r\n pnpm: 8.14.3 - E:\\nodejs\\node_global\\pnpm.CMD\r\n Browsers:\r\n Edge: Chromium (120.0.2210.144)\r\n Internet Explorer: 11.0.19041.3636\r\n npmPackages:\r\n vitepress: 1.0.0-rc.40 => 1.0.0-rc.40\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.",[3229],{"name":3230,"color":3231},"question","5D5FAE",3513,"部署到Github Pages之后,如果使用自定义域名的话样式会丢失","2024-02-07T00:04:15Z","https://github.com/vuejs/vitepress/issues/3513",0.695358,{"description":3238,"labels":3239,"number":3244,"owner":3158,"repository":3159,"state":3160,"title":3245,"updated_at":3246,"url":3247,"score":3248},"### Describe the bug\r\n\r\nWhen I:\r\n- installed 'vitepress v1.0.0-rc.25' and executed 'npm run docs: dev', any image displayed normally.\r\n- installed 'vitepress v1.0.0-rc.26' and executed 'npm run docs: dev', any image displayed a 404 error. After manually adding the prefix {vitepressconfig. base} before the path of the image in the domElementPanel(devtool), it displayed normally.\r\n\r\nThe problem of compilating wrong assets path does not have any issues in production environment (when you 'npm run docs: build' and 'npm run docs: preview'), only occurs in the development environment.\r\n\r\n### Reproduction\r\n\r\nInit project\r\n```\r\nnpm i -D vitepress@vitepress v1.0.0-rc.26\r\nnpx vitepress init\r\n/* choosed this options\r\nWhere should VitePress initialize the config? \"./docs\"\r\nTheme: Default Theme (Out of the box, good-looking docs)\r\n*/\r\n```\r\n\r\nCreate directory structure\r\n```\r\ndocs/\r\n .vitepress/\r\n config.mts\r\n assets/\r\n image/\r\n cat.png\r\n index.md\r\n```\r\n\r\nAdd ` base` property in `.vitepress/config.mts`\r\n```\r\nimport { defineConfig } from \"vitepress\";\r\nexport default defineConfig({\r\nbase:'/base/'\r\n})\r\n```\r\n\r\nAdd a image in `index.md`\r\n``\r\n\r\nStart development environment\r\n`npm run docs:dev`\r\n\r\nThen, in the network-panel(chrome dev-tool) you will find that the image request is 404.\r\nopen the dom-panel and modify the image path from '/assets/image/cat. png' to '/base/assets/image/cat. png', it will be normal.\r\n\r\nHowever, if you install `vitepress@vitepress V1.0.0-rc.25`, everything is normal. It seems that there has been a breaking-change in the asset path compilation, but I did not see it in the CHANGLOG.\r\n\r\n\r\n### Expected behavior\r\n\r\nIn the development environment\r\n```\r\n/base/assets/image/cat.png` // it's wrong,please don't compile to this\r\n/assets/image/cat.png // it's correct!\r\n```\r\n\r\n### System Info\r\n\r\n```\r\nSystem:\r\n OS: macOS 13.6.1\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz\r\n Memory: 1.97 GB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\nBinaries:\r\n Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node\r\n npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm\r\nBrowsers:\r\n Chrome: 119.0.6045.159\r\n Edge: 119.0.2151.72\r\n Safari: 17.1\r\nnpmPackages:\r\n vitepress: ^1.0.0-rc.29 => 1.0.0-rc.29`\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI really want to fix this issue, but I can't located yet😢 ...\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.",[3240,3241],{"name":3188,"color":3189},{"name":3242,"color":3243},"upstream","BF29ED",3239,"Compiled a wrong asset path(‘/base/’ prefix) in the development environment","2023-12-03T00:04:52Z","https://github.com/vuejs/vitepress/issues/3239",0.70109785,{"description":3250,"labels":3251,"number":3253,"owner":3158,"repository":3159,"state":3160,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### Describe the bug\n\nIf I enable localSearch in the theme config, markdown files in public dir are considered as if they are in the content dir and be processed by vitepress. This is unwanted.\n\n### Reproduction\n\nEnable localSearch and add markdown some files in the public dir.\n\n### Expected behavior\n\nPublic dir should not be processed by vitepress.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.19 Ubuntu 22.10 22.10 (Kinetic Kudu)\r\n CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz\r\n Memory: 4.08 GB / 7.21 GB\r\n Container: Yes\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.0.0 - ~/.local/share/pnpm/node\r\n npm: 9.6.2 - ~/.local/share/pnpm/npm\r\n Browsers:\r\n Chrome: 112.0.5615.49\r\n```\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.",[3252],{"name":3152,"color":3153},2209,"localSearch treat public dir as content","2023-04-20T00:03:59Z","https://github.com/vuejs/vitepress/issues/2209",0.7011984,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fsIQ47g91N7XAHiiL-8mNL41iOktLgGZux8bWZkAJ9dY":-1},"/vuejs/vitepress/2053"]