\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.",[3188],{"name":3189,"color":3190},"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.6787402,{"description":3197,"labels":3198,"number":285,"owner":3152,"repository":3153,"state":3163,"title":3199,"updated_at":3200,"url":3201,"score":3202},"Following the steps from `README.md`\r\n\r\n```sh\r\n~/development/playground/vitepress_test\r\n❯ echo '# Hello VitePress' > index.md\r\n\r\n~/development/playground/vitepress_test\r\n❯ npx vitepress\r\nvitepress v0.2.0\r\nvite v0.16.7\r\nlistening at http://localhost:3000\r\n\r\n Error: ENOENT: no such file or directory, stat '/Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/dist/client/app/index.html'\r\n at Object.statSync (fs.js:1035:3)\r\n at Object.statSync (/Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/node_modules/graceful-fs/polyfills.js:308:16)\r\n at Object.cachedRead (/Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/node_modules/vite/dist/utils/fsUtils.js:20:45)\r\n at /Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/dist/node/server.js:98:30\r\n at async /Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/node_modules/vite/dist/server/serverPluginHtml.js:51:9\r\n at async /Users/ziga/.npm/_npx/21240/lib/node_modules/vitepress/node_modules/vite/dist/server/serverPluginModuleRewrite.js:25:9\r\n```\r\n\r\ncauses **Error: ENOENT**.\r\n\r\nI believe it originates from [resolver's APP_PATH](https://github.com/vuejs/vitepress/blob/master/src/node/resolver.ts#L4)",[],"Wrong APP_PATH","2023-01-21T16:25:42Z","https://github.com/vuejs/vitepress/issues/15",0.6823766,{"description":3204,"labels":3205,"number":3207,"owner":3152,"repository":3153,"state":3163,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Describe the bug\r\n\r\nUsing Monaco Editor (applying **[this trick](https://github.com/vuejs/vitepress/issues/1508)**) works with `npm run docs:dev` but is failing with `npm run docs:build`\r\n\r\nIn other words, Monaco Editor works in dev but fails in build. The is **not** related to imports ([ex1](https://github.com/vuejs/vitepress/issues/1508), [ex2](https://github.com/vitejs/vite/discussions/1791#discussioncomment-321046, [ex3](https://twitter.com/youyuxi/status/1355316139144970240?s=20))\r\n\r\nThe error when building reads is about module_not_found (the package is definitely installed & path exists):\r\n\r\n```\r\nError [ERR_MODULE_NOT_FOUND]: Cannot find package '/home/projects/nbwixzanm.github/node_modules/monaco-editor/' imported from /home/projects/nbwixzanm.github/.vitepress/.temp/....\r\n```\r\n\r\nStackblitz:\r\n\u003Cimg width=\"1040\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/1396559/1ce6110a-4d0e-4160-a1df-9148f778ebe3\">\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/valgaze/vitepress-monaco#setup\r\n\r\nhttps://stackblitz.com/github/valgaze/vitepress-monaco # npm run docs:build\r\n\r\n### Expected behavior\r\n\r\nMonaco Editor should be able to build/bundle and find its folder that exists\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: macOS 12.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 139.38 MB / 16.00 GB\r\n Shell: 3.2.57 - /bin/bash\r\n Binaries:\r\n Node: 18.11.0 - ~/.nvm/versions/node/v18.11.0/bin/node\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.11.0/bin/npm\r\n Browsers:\r\n Brave Browser: 114.1.52.122\r\n Chrome: 116.0.5845.96\r\n Firefox: 105.0.3\r\n Safari: 15.2\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.4 => 1.0.0-rc.4\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.",[3206],{"name":3146,"color":3147},2832,"Monaco-editor + Vitepress not found on 1.0.0-rc.4 when building?","2023-08-31T00:04:23Z","https://github.com/vuejs/vitepress/issues/2832",0.68473244,{"description":3213,"labels":3214,"number":3218,"owner":3152,"repository":3153,"state":3163,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### Discussed in https://github.com/vuejs/vitepress/discussions/527\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **WebMechanic** February 11, 2022\u003C/sup>\r\nHello,\r\n\r\nI have a fresh install of VitePress to document our new Style Guide and wanted to use the [Import Code Snippets](https://vitepress.vuejs.org/guide/markdown.html#import-code-snippets) feature for .js, .css and .html fragments, but the file(s) are not included. I tried all sorts of pathnames with/without the `base`, relative, absolute, all to no avail.\r\nEverything else works like a charme.\r\n\r\nThe project is a simple Vite Vue project. I then installed VitePress with yarn. \r\nIt resides in `src/_docs/.vitepress`.\r\n\r\nHere's the config file\r\n```js\r\nimport {defineConfig} from 'vitepress'\r\nexport default defineConfig({\r\n base: '/src/_docs/',\r\n title: \"The Style Guide\",\r\n markdown: {\r\n lineNumbers: false,\r\n toc: {includeLevel: [1, 2]},\r\n }\r\n}\r\n```\r\n\u003C/div>\r\n\r\nIt's not clear to me, if this requires some special care for Prism. Configuration seems very different fro what I can find on Lea Verou's site.\r\n",[3215],{"name":3216,"color":3217},"invalid","ffffff",530,"\"Import Code Snippets\" not working","2023-01-21T16:04:03Z","https://github.com/vuejs/vitepress/issues/530",0.68583614,{"description":3224,"labels":3225,"number":3227,"owner":3152,"repository":3153,"state":3163,"title":3228,"updated_at":3229,"url":3230,"score":3231},"**Describe the bug**\r\n\r\nSee https://github.com/songololo/vitepress-debug for reproduction of this issue:\r\n\r\nRun a dev server: `yarn docs:dev`.\r\n\r\nNote that the base-path `/my-base-path/` is set in the config at `.vitepress/config.js`.\r\n\r\nThe base path works for root files, i.e. `index.md` is served from `/my-base-path/`.\r\n\r\nHowever, the base path is missing for nested files, i.e. `content/index.md` is served from `/content/` and `content/hello.md` is served from `/content/hello.html`.\r\n\r\nThis doesn't break things in development mode because the links are also missing the base path.\r\n\r\nHowever, it breaks things in production because the links are missing the base path.\r\n\r\n**System Info**\r\n- vitepress 0.12.2\r\n- vite/2.0.4\r\n- darwin-x64\r\n- node-v15.8.0\r\n\r\nThis happens for both my local system and for a github actions build.",[3226],{"name":3146,"color":3147},252,"Base paths (and links) not generating correctly for nested pages.","2023-01-21T16:20:10Z","https://github.com/vuejs/vitepress/issues/252",0.6863811,{"description":3233,"labels":3234,"number":3235,"owner":3152,"repository":3153,"state":3163,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Is your feature request related to a problem? Please describe.\r\n\r\nI'm using vitepress in an existing project for documentation, and I want to keep the docs build in a separate directory for instance:\r\n\r\n```\r\ndocs\r\n - assets\r\n - xxx.js\r\n - index.html\r\nsrc\r\n - App.vue\r\n```\r\n\r\nBut I can't load `/docs/index.html` since the assets use an absolute url `/assets/xxx.js`.\r\n\r\n### Describe the solution you'd like\r\n\r\nCan we allow relative url in the `index.html` so that when loading `docs/index.html` it's still working ?\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/coc)\r\n- [X] Read the [docs](https://vitepress.vuejs.org/).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],381,"Allow relative path for assets / scripts in out index.html","2023-01-21T14:33:00Z","https://github.com/vuejs/vitepress/issues/381",0.68649197,["Reactive",3241],{},["Set"],["ShallowReactive",3244],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fi0Nb8aLLdwDadiyz5TP-OePTNPspZlp7gdPvRqnFyvA":-1},"/vuejs/vitepress/610"]