\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.69710916,{"description":3207,"labels":3208,"number":3209,"owner":3149,"repository":3150,"state":3151,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Is your feature request related to a problem? Please describe.\n\nThe `assets` in `dist` is too messy. I want to get an organized `dist`\n\n### Describe the solution you'd like\n\nwhen i try to use `build.rollupOptions.output.assetFileNames` in `vite.config.js`, it doesn't take effect\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.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.",[],1938,"split `dist/assets` and file them into appropriate subfolders","2023-03-23T00:04:26Z","https://github.com/vuejs/vitepress/issues/1938",0.70005065,{"description":3215,"labels":3216,"number":3217,"owner":3149,"repository":3150,"state":3151,"title":3218,"updated_at":3219,"url":3220,"score":3221},"**Describe the bug**\r\nTo set 'base' property in '.vitepress/config.js', and run 'vitepress dev docs' behind nginx. When access it, the 'index.js' can't be loaded. Because it's path missed 'base' path. \r\nServer response like this:\r\n``` html\r\n\u003C!DOCTYPE html>\r\n\u003Chtml>\r\n \u003Chead>\r\n \u003Cmeta charset=\"utf-8\">\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cdiv id=\"app\">\u003C/div>\r\n \u003Cscript type=\"module\" src=\"/@fs//xxxxxxxxx/doc-index/node_modules/vitepress/dist/client/app/index.js\">\u003C/script>\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\nI set the base is '/docs/'. So, the path of 'index.js' shuld be: \r\n``` html \r\n/docs/@fs//xxxxxxxxx/doc-index/node_modules/vitepress/dist/client/app/index.js\r\n```\r\n\r\nBy the way, line number 131 of 'vitepress/src/node/plugin.js' shuld be: \r\n``` html\r\n\u003Cscript type=\"module\" src=\"${siteData.base}@fs/${APP_PATH}/index.js\">\u003C/script>\r\n```\r\n\r\n**System Info**\r\n- vitepress version: 0.14.1\r\n- vite version: 2.3.7\r\n- Node version: v12.8.1\r\n- OS version: Windows 10 pro 21H1 19043.1055\r\n",[],319,"missed 'base' path when run 'vitepress dev docs' behind nginx","2023-01-21T14:32:44Z","https://github.com/vuejs/vitepress/issues/319",0.7013342,{"description":3223,"labels":3224,"number":3228,"owner":3149,"repository":3150,"state":3151,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Describe the bug\r\n\r\nMy project is an es-modules-project (type=\"modules\" in package.json). I run Node v16.1.0.\r\n\r\nI added a `vite.config.ts` to my `/docs` folder to include WindiCSS in my Vitepress project:\r\n```ts\r\n// vite.config.ts\r\nimport { defineConfig } from 'vite';\r\nimport WindiCSS from 'vite-plugin-windicss';\r\n\r\nexport default defineConfig({\r\n plugins: [WindiCSS()],\r\n});\r\n```\r\n\r\nI use the environment variable `--experimental-specifier-resolution=node` for running the scripts:\r\n```\r\n// package.json\r\n{\r\n// ...\r\n \"scripts\": {\r\n \"docs:dev\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress dev docs\",\r\n \"docs:build\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress build docs\",\r\n \"docs:serve\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress serve docs\"\r\n }\r\n// ...\r\n}\r\n```\r\n\r\ndocs:dev still works fine. But when I rund docs:build an error occurs:\r\n\r\n```sh\r\nfailed to load config from /home/project/docs/vite.config.ts\r\n✖ building client + server bundles...\r\nbuild error:\r\n Error: ENOENT: no such file or directory, unlink '/home/project/docs/vite.config.ts.js'\r\n at Object.unlinkSync (node:fs:1709:3)\r\n at loadConfigFromFile (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:71321:29)\r\n at async resolveConfig (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:70861:28)\r\n at async doBuild (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:38954:20)\r\n at async Object.build (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:38942:16)\r\n at async Promise.all (index 1)\r\n at async bundle (/home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js:40814:36)\r\n at async Object.build (/home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js:41015:59) {\r\n errno: -2,\r\n syscall: 'unlink',\r\n code: 'ENOENT',\r\n path: '/home/project/docs/vite.config.ts.js'\r\n}\r\n```\r\n\r\nIf I rename the `vite.config.ts` to `vite.config.js` it seems that the build process continues until the next error occurs:\r\n\r\n```sh\r\nError [ERR_REQUIRE_ESM]: Must use import to load ES Module: /home/chd/gettherapie-webseite/cim-elements/docs/.vitepress/.temp/app.js\r\nrequire() of ES modules is not supported.\r\nrequire() of /home/project/docs/.vitepress/.temp/app.js from /home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js is an ES module file as it is a .js file whose nearest parent package.json contains \"type\": \"module\" which defines all .js files in that package scope as ES modules.\r\nInstead rename app.js to end in .cjs, change the requiring code to use import(), or remove \"type\": \"module\" from /home/project/docs/package.json.\r\n```\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nSee above\r\n\r\n### Expected behavior\r\n\r\nbuild should finish successfully\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 4.19 Ubuntu 20.04 LTS (Focal Fossa)\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\r\n Memory: 1.38 GB / 19.55 GB\r\n Container: Yes\r\n Shell: 5.0.16 - /bin/bash\r\n Binaries:\r\n Node: 16.1.0 - /usr/local/bin/node\r\n Yarn: 3.1.1 - ~/.yarn/bin/yarn\r\n npm: 7.11.2 - /usr/local/bin/npm\r\n npmPackages:\r\n vitepress: ^0.22.2 => 0.22.2\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nThe project runs under a yarn workspace monorepo\r\n\r\nIf I remove the vite.config.ts the build works fine.\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3225],{"name":3226,"color":3227},"build","377ba8",537,"Build not working with vite.config.ts and es-modules","2023-01-21T14:25:14Z","https://github.com/vuejs/vitepress/issues/537",0.70480245,{"description":3234,"labels":3235,"number":3237,"owner":3149,"repository":3150,"state":3151,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Describe the bug\n\nImage wasn't inlined, see https://stackblitz.com/edit/vite-upxxuh?file=package.json,vite.config.ts:\r\n\r\n\u003Cimg width=\"1919\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/3367820/7ab7ef71-c29e-4a24-9f96-36d06441e7b9\">\r\n\n\n### Reproduction\n\nsee https://stackblitz.com/edit/vite-upxxuh?file=package.json,vite.config.ts:\r\n\r\n\u003Cimg width=\"1919\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/3367820/7ab7ef71-c29e-4a24-9f96-36d06441e7b9\">\n\n### Expected behavior\n\nthe image should be base64 inlined according to https://vitepress.dev/guide/asset-handling#referencing-static-assets\n\n### System Info\n\n```Text\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.18.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.2 - /usr/local/bin/npm\r\n pnpm: 8.10.5 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: v1.0.0-beta.7 => 1.0.0-beta.7\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.",[3236],{"name":3168,"color":3169},3370,"assets Inline doesn't work?","2023-12-30T00:04:35Z","https://github.com/vuejs/vitepress/issues/3370",0.7060798,["Reactive",3243],{},["Set"],["ShallowReactive",3246],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fO0UTsntgnfGA3kimv7Loayah0fk6RuoTfTH_ePx98hA":-1},"/vuejs/vitepress/3984"]