\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.",[3178],{"name":3179,"color":3180},"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.69680464,{"description":3187,"labels":3188,"number":3195,"owner":3149,"repository":3150,"state":3151,"title":3196,"updated_at":3197,"url":3198,"score":3199},"### Describe the bug\r\n\r\nNot sure if a bug or user error. Should this work? (check reproduction)\r\n\r\n### Reproduction\r\n\r\n```ts\r\nconst githubRepo = resolve(__dirname, '..', '..', '.github', 'docs')\r\nlet rewrites = {}\r\nrewrites[resolve(githubRepo, 'SECURITY.md')] = 'policy/security'\r\n\r\nexport default defineConfig({\r\n // ...\r\n rewrites,\r\n // ...\r\n})\r\n```\r\n\r\n### Expected behavior\r\n\r\nNavigating to https://siteurl/policy/security should load content from the .github repo source\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: macOS 13.3.1\r\n CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz\r\n Memory: 68.12 MB / 24.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.9.1 - ~/.nvm/versions/node/v18.9.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.9.1/bin/yarn\r\n npm: 9.4.0 - ~/.nvm/versions/node/v18.9.1/bin/npm\r\n Browsers:\r\n Chrome: 112.0.5615.137\r\n Safari: 16.4\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.74 => 1.0.0-alpha.74\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nA quick `console.log` of the config shows the correct path is loaded under the rewrite object.\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.",[3189,3192],{"name":3190,"color":3191},"bug: pending triage","e99695",{"name":3193,"color":3194},"stale","ededed",2335,"Rewrite routes with path outside project root ","2023-08-20T00:04:17Z","https://github.com/vuejs/vitepress/issues/2335",0.6998103,{"description":3201,"labels":3202,"number":3203,"owner":3149,"repository":3150,"state":3151,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### Is your feature request related to a problem? Please describe.\r\n\r\nCurrently, I have three small blogs due to different approaches. I have customized certain things in the theme design when downloading VitePress, for example, to include in these projects native web components that can be loaded as an html tag from a simple Markdown (.md) file, besides include TailwindCSS.\r\nI am not interested in doing a Fork and would like to evaluate if it is possible to change the directory of the Vitepress documents (separating or decoupling the content of the mechanism) in order to have versatility and not having to copy in each project folder the theme and components (I mean, an `srcDir` different from `root`).\r\n\r\n### Describe the solution you'd like\r\n\r\nOne idea would be to allow the base directory of Vitepress to be different from the root, separating or decoupling the content of the theme or template (although I would understand if it is a matter of design).\r\nWhat is wanted is to use the modified Vitepress theme on different blogs without having to copy it to each project (thinking in multi-project of content)\r\n\r\n### Describe alternatives you've considered\r\n\r\n1. I have tried to apply on each of the three Vitepress blogs with the custom theme ( just that it can lead to theme desynchronization).\r\n\r\n2. Another way is to have every blog under root folder and change `srcDir` in `config.mjs` according the blog selected.\r\n\r\n3. Using a symbolic link but eventualy some errors occurs cause it resolves another path (e.g. `../../path`) and finally doesn't work.\r\n\r\n### Additional context\r\n\r\nThe project with native web components that can be use in Markdown (.md) is: \u003Chttps://github.com/kaesar/onmind-cui>\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.",[],4384,"A way to configure the directory for docs instead of the root folder","2024-12-29T04:43:47Z","https://github.com/vuejs/vitepress/issues/4384",0.70039,{"description":3209,"labels":3210,"number":3211,"owner":3149,"repository":3150,"state":3151,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Discussed in https://github.com/vuejs/vitepress/discussions/609\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **Roman-00** April 25, 2022\u003C/sup>\r\nWhen hosting, I have already brought down this project for hosting in a subdirectory https://domain.com/ms/guide , can't get to js files and styles, writes 404. How can I specify the path to styles and js files when building\r\n\r\n\r\nCan I somehow register the path to the files myself within vitepress?\u003C/div>",[],610,"When hosting, I have already brought down this project for hosting in a subdirectory https://domain.com/ms/guide , can't get to js files and styles, writes 404","2023-01-21T16:04:28Z","https://github.com/vuejs/vitepress/issues/610",0.7017445,{"description":3217,"labels":3218,"number":3220,"owner":3149,"repository":3150,"state":3151,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Describe the bug\r\n\r\nVitePress builds, and instantly removes the dist folder again.\r\n\r\n### Reproduction\r\n\r\nClone my [GitHub repository](https://github.com/Ahwxorg/Linkbase/), run yarn to install the dependencies and run `yarn vitepress build`.\r\n\r\n### Expected behavior\r\n\r\nVitePress successfully builds the dist/ folder.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 13.5.2\r\n CPU: (10) arm64 Apple M2 Pro\r\n Memory: 125.69 MB / 16.00 GB\r\n Shell: 3.6.1 - /opt/homebrew/bin/fish\r\n Binaries:\r\n Node: 20.7.0 - /opt/homebrew/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 10.1.0 - /opt/homebrew/bin/npm\r\n Browsers:\r\n Safari: 16.6\r\n```\r\n\r\n\r\nAlthough I use GitHub Actions as well (see [the failed run here](https://github.com/Ahwxorg/Linkbase/actions/runs/6273423931/job/17036870482))\r\n\r\n\r\n### Additional context\r\n\r\nBuild log is the following:\r\n\r\n```sh\r\nvitepress v1.0.0-rc.20\r\n\r\n✓ building client + server bundles...\r\n✓ rendering pages...\r\nbuild complete in 1.89s.\r\n✨ Done in 2.06s.\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.",[3219],{"name":3190,"color":3191},3040,"[Bug] VitePress won't build","2023-10-10T00:04:18Z","https://github.com/vuejs/vitepress/issues/3040",0.70431936,{"description":3226,"labels":3227,"number":3228,"owner":3149,"repository":3150,"state":3151,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Is your feature request related to a problem? Please describe.\n\nCurrently Vitepress requires this directory structure:\r\n\r\n```\r\n.\r\n├─ docs\r\n│ ├─ .vitepress\r\n│ │ └─ config.js\r\n│ └─ index.md\r\n└─ package.json\r\n```\r\n\r\nBut I just want to use Vitepress in a non-JS project, so I don't want `package.json` at my project root.\n\n### Describe the solution you'd like\n\nI want to have `package.json` under the `docs/` dir alongside the `.vitepress` config dir and `index.md`:\r\n\r\n```\r\n.\r\n├─ .git\r\n├─ docs\r\n│ ├─ .vitepress\r\n│ │ └─ config.js\r\n│ ├─ pt-br\r\n│ │ └─ index.md\r\n│ ├─ package.json\r\n│ └─ index.md\r\n└─ rest of my project\r\n```\n\n### Describe alternatives you've considered\n\nHaving nested `docs/` directories works but is cumbersome:\r\n\r\n```\r\n.\r\n├─ .git\r\n├─ docs\r\n│ ├─ docs\r\n│ │ ├─ .vitepress\r\n│ │ │ └─ config.js\r\n│ │ ├─ pt-br\r\n│ │ │ └─ index.md\r\n│ │ └─ index.md\r\n│ └─ package.json\r\n└─ rest of my project\r\n```\n\n### Additional context\n\nI have been using Vuepress with `vuepress-vite@2.0.0-beta.22` this way, but haven't been keeping up with it's updates, so it might have changed this behaviour in a more recent Beta release, I am not sure.\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] 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.",[],844,"Support for other directory structures for use in non-JS projects","2023-01-21T14:33:59Z","https://github.com/vuejs/vitepress/issues/844",0.70870346,{"description":3234,"labels":3235,"number":3238,"owner":3149,"repository":3150,"state":3151,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Describe the bug\r\n\r\nI have a my node_modules as symlink, for save space and prevent synch with the cloud storage. Vite has some problemens resolving path with symlink, because they actually outside of the root folder, so they aren't in the allow list. This can be solved with `server.fs.strict= false`. But in vitepress, doesn't exist `vite.config.js`, I already tried to put in `./vitepress/config.js` but still got the same error.\r\n\r\n### Reproduction\r\n\r\n1. create a \"node_module\" as symlink, the original folder must be outside of the root.\r\n2. install the dependencies\r\n3. run dev\r\n\r\n### Expected behavior\r\n\r\ndev should run normally.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (4) x64 Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz\r\n Memory: 451.46 MB / 3.88 GB\r\n Binaries:\r\n Node: 18.12.1 - C:\\ProgramData\\Anaconda3\\node.EXE\r\n npm: 9.2.0 - C:\\ProgramData\\Anaconda3\\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\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.",[3236,3237],{"name":3179,"color":3180},{"name":3193,"color":3194},2443,"vitepress doesn't work with node_modules as symlink","2023-09-07T00:04:18Z","https://github.com/vuejs/vitepress/issues/2443",0.7099148,["Reactive",3244],{},["Set"],["ShallowReactive",3247],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgabY8zcxRl_VAwTFBHNQJU-z_9OUPw_Efo3_W6mZT-A":-1},"/vuejs/vitepress/2716"]