\r\n\r\nbut in Layout.vue it uses Header and Header uses themeConfig that is a Symbol: \r\n```vue\r\n// Layout.vue\r\n\u003Ctemplate>\r\n \u003CHeader :nav=\"Navlist\">\u003C/Header>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport Header from \"../header/index.vue\";\r\n\u003C/script>\r\n// Header.vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { inject, computed } from \"vue\";\r\nimport { themeConfig } from \"../../compositions/configProvider\"; // Notice this line\r\n\r\nconst theme = inject(themeConfig)!; // Notice this line\r\n```\r\nIn Header.vue, themeConfig exists in myTheme/src/compositions/configProvider.ts, \r\nbut in .vitepress/cache/deps/myTheme.js, it also exits a themeConfig.\r\ntwo themeConfig, two Symbol.\r\n***In the result***, provide/inject is fail.\r\n\r\n\r\nIn development this is bad, in production, the configProvider module is not extracted, the themeConfig variable is unique.\n\n### Reproduction\n\nas mentioned earlier\n\n### Expected behavior\n\nIn development, some es module that come from node_modules ain't extracted, the variable don't be duplicated.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11 10.0.22000\r\n Binaries:\r\n Node: 18.16.0\r\n pnpm: 8.6.0\r\n npmPackages:\r\n vitepress: 1.0.0-rc.31\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.",[2881,2884],{"name":2882,"color":2883},"need more info","bdbefc",{"name":2868,"color":2869},3292,"Theme is made into npm package, if use the theme, Symbol is duplicated in dev.","2024-03-07T11:19:22Z","https://github.com/vuejs/vitepress/issues/3292",0.8127364,{"description":2891,"labels":2892,"number":2893,"owner":2871,"repository":2872,"state":2873,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### Is your feature request related to a problem? Please describe.\n\n这个太cool了,会有uniapp版本嘛?\n\n### Describe the solution you'd like\n\n这个太cool了,会有uniapp版本嘛?\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.",[],4572,"这个太cool了,会有uniapp版本嘛?","2025-02-21T13:30:50Z","https://github.com/vuejs/vitepress/issues/4572",0.82201195,{"description":2899,"labels":2900,"number":2904,"owner":2871,"repository":2872,"state":2905,"title":2906,"updated_at":2907,"url":2908,"score":2909},"### Describe the bug\n\nFor example:\r\nIf the markdown filename is `01 overview.md`, and the link of this file in `.vitepress/config.ts` is `link: 'path/to/01 overview' `,\r\nthen:\r\n1. If I run `docs:dev`, I can access this page by `path/to/01%20overview`, everything works well.\r\n2. If I run `docs:build`, it doesn't work, and return 404\n\n### Reproduction\n\nAs above\n\n### Expected behavior\n\nblank character in markdown file's filename should still work after build \n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz\r\n Memory: 6.17 GB / 15.92 GB\r\n Binaries:\r\n Node: 18.16.0 - D:\\Program Files\\NodeJS\\node.EXE\r\n npm: 9.6.4 - D:\\Program Files\\NodeJS\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.58)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: latest => 1.0.0-alpha.74\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.",[2901],{"name":2902,"color":2903},"build","377ba8",2296,"closed","` ` character (%20) in markdown filename cannot work after build","2023-05-08T00:04:06Z","https://github.com/vuejs/vitepress/issues/2296",0.78022957,{"description":2911,"labels":2912,"number":2913,"owner":2871,"repository":2872,"state":2905,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Is your feature request related to a problem? Please describe.\n\n```txt\r\ndocs/\r\n├─ en/\r\n│ ├─ foo.md\r\n├─ zh/\r\n│ ├─ foo.md\r\n├─ fr/\r\n ├─ foo.md\r\n```\r\n\r\n对于以上多语言结构,默认路由为:`/en/` `/zh/` `/fr/`,没办法设置 `/` 默认语言展示。\n\n### Describe the solution you'd like\n\n设置 `/` 默认展示语言,或者将 `/` 路由重定向到默认语言路由 `/zh/`\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.",[],2948,"多语言情况下设置默认语言","2023-09-20T00:04:18Z","https://github.com/vuejs/vitepress/issues/2948",0.8029419,{"description":2919,"labels":2920,"number":2924,"owner":2871,"repository":2872,"state":2905,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Is your feature request related to a problem? Please describe.\n\nWhen you put build and deployment into the CI it happens from time to time that \"dead links\" exist.\n\n### Describe the solution you'd like\n\nI would like to have a way to manually run the dead links search step (and other steps if needed). This would allow me to run a light test script on the feature branches to know how the deploy will be before the merge into the deploy branch. \n\n### Describe alternatives you've considered\n\nOf course, I could also run the build on the feature branch. But this seems to me (especially for larger projects) rather more cumbersome and resource-intensive.\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.",[2921],{"name":2922,"color":2923},"has-workaround","1B4515",2878,"feat: build dry run or verify option","2023-09-08T00:04:10Z","https://github.com/vuejs/vitepress/issues/2878",0.8036873,{"description":2930,"labels":2931,"number":2935,"owner":2871,"repository":2872,"state":2905,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the bug\n\n``` flow\r\nst=>start: 开始\r\nprocess1=>operation: 语句1\r\nprocess2=>operation: 语句2\r\nprocess3=>operation: 语句3\r\ne=>end: 结束\r\n\r\nst->process1->process2->process3->e\r\n```\n\n### Reproduction\n\nN/A\n\n### Expected behavior\n\n\r\n\n\n### System Info\n\n```shell\nN/A\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.",[2932],{"name":2933,"color":2934},"bug: pending triage","e99695",1233,"No language registration for flow","2023-01-21T14:26:53Z","https://github.com/vuejs/vitepress/issues/1233",0.80811876,{"description":2941,"labels":2942,"number":2944,"owner":2871,"repository":2872,"state":2905,"title":2945,"updated_at":2946,"url":2947,"score":2877},"### Describe the bug\n\nRelative download link to a zip attachment in md file is broken after build.\r\n\r\nOr Maybe it is a feature?\n\n### Reproduction\n\nI've got the markdown file like this:\r\n\r\n`test.md:`\r\n``` markdown\r\nYou can [download](./test.assets/tools.zip) the script files.\r\n```\r\n\r\nThe file structure like this:\r\n```\r\nU:\\Readme\\Tools\\test>tree /f\r\n卷 working 的文件夹 PATH 列表\r\n卷序列号为 0B18-4870\r\nU:.\r\n│ test.md\r\n│\r\n└─test.assets\r\n Tools.zip\r\n```\r\n\r\nNow the typora editor can click the zip link, works fine.\r\n\r\nTypora export to html file, works fine, too.\r\n\r\n`yarn docs:dev`, works fine, too.\r\n\r\n`yarn docs:build`, the link is broken, and get 404.\r\n\r\nI don't want to copy the zip file to other places because I'd like the assets folder shipped with the md file. The zip file is a part of the test.md. So it is not a good idea to place them to different place.\r\n\r\nSo, is it a feature, or a bug?\n\n### Expected behavior\n\nI wish it can work as same as docs:dev.\n\n### System Info\n\n```shell\nWindows 11\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.",[2943],{"name":2882,"color":2883},1485,"Relative download link to a zip attachment in md file is broken after build.","2023-01-21T14:22:51Z","https://github.com/vuejs/vitepress/issues/1485",{"description":2949,"labels":2950,"number":2952,"owner":2871,"repository":2872,"state":2905,"title":2953,"updated_at":2954,"url":2955,"score":2877},"### Describe the bug\n\nI'm really sorry to bother the vitepress developers with such a small problem, I love vitepress, but now run into problems that I can't solve. I try to build the production version and always report errors as shown but from the error stack I can t find the root of the problem it looks a lot like a bug inside vitepress and probably also because my limited personal level caused me unable to solve it so I decided to mention this issues.\r\n\n\n### Reproduction\n\nnpm run docs:build\n\n### Expected behavior\n\nSuccessfully get the construction product\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.22000\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz\r\n Memory: 1.15 GB / 7.86 GB\r\n Binaries:\r\n Node: 16.16.0 - G:\\Nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.11.0 - G:\\Nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22000.120.0), Chromium (106.0.1370.52)\r\n Internet Explorer: 11.0.22000.120\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.25 => 1.0.0-alpha.25\n```\n\n\n### Additional context\n\n\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.",[2951],{"name":2882,"color":2883},1541,"The error when constructing the product","2023-01-21T14:20:47Z","https://github.com/vuejs/vitepress/issues/1541",{"description":2957,"labels":2958,"number":2960,"owner":2871,"repository":2872,"state":2905,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Describe the bug\n\nThere seems to be an error with using multiline configs in the Frontmatter. The error is best seen in attempting to recreate the Hero and Features sections from the Frontmatter Configs docs.\r\n\r\n## Hero\r\nWhen attempting to recreate the [hero section from the docs](https://vitepress.vuejs.org/config/frontmatter-configs#hero), I get the following error: \r\n\r\n```\r\n[vite] Internal server error: duplicated mapping key at line 10, column 4:\r\n text: Get Started\r\n ^\r\n```\r\n\r\n👉 Removing the actions such that the Frontmatter only contains the code below, does not result in an error of any kind but does not render anything on the page.\r\n\r\n```md\r\n---\r\nlayout: home\r\n\r\nhero:\r\n name: VuePress\r\n text: Vite & Vue powered static site generator.\r\n tagline: Lorem ipsum...\r\n---\r\n```\r\n\r\n## Features\r\nSimilarly, in attempting to recreate the [features section](https://vitepress.vuejs.org/config/frontmatter-configs#features) I get the error:\r\n\r\n```\r\n[vite] Internal server error: end of the stream or a document separator is expected at line 8, column 2:\r\n - icon: 🖖\r\n ^\r\n```\r\n👉 Removing all but one feature, as shown in the code below, does not give errors but results in only icon being displayed.\r\n\r\n```md\r\n---\r\nlayout: home\r\n\r\nfeatures:\r\n - icon: ⚡️\r\n title: Vite, The DX that can't be beat\r\n details: Lorem ipsum...\r\n---\r\n```\r\n\r\n\u003Cimg width=\"555\" alt=\"image\" src=\"https://user-images.githubusercontent.com/69503530/187670575-04cf7cfe-68da-44f4-9094-183b79bced58.png\">\r\n\r\n👉 Removing the icon field results in the following:\r\n\r\n```md\r\n---\r\nlayout: home\r\n\r\nfeatures:\r\n - title: Vite, The DX that can't be beat\r\n details: Lorem ipsum...\r\n---\r\n```\r\n\u003Cimg width=\"490\" alt=\"image\" src=\"https://user-images.githubusercontent.com/69503530/187670887-7ea23b49-93fb-470b-aafb-7f7311fa63f1.png\">\r\n\r\n\n\n### Reproduction\n\nFile containing the exact code as per the hero section of the docs:\r\n\r\n```md\r\n---\r\nlayout: home\r\n\r\nhero:\r\n name: VuePress\r\n text: Vite & Vue powered static site generator.\r\n tagline: Lorem ipsum...\r\n actions:\r\n - theme: brand\r\n text: Get Started\r\n link: /guide/what-is-vitepress\r\n - theme: alt\r\n text: View on GitHub\r\n link: https://github.com/vuejs/vitepress\r\n---\r\n```\n\n### Expected behavior\n\nReproduce the hero section as per the docs\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 98.45 MB / 8.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.17.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 8.15.0 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 104.0.5112.101\r\n Safari: 15.2\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.13 => 1.0.0-alpha.13\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.",[2959],{"name":2882,"color":2883},1265,"Frontmatter config not behaving as expected","2023-01-21T14:26:46Z","https://github.com/vuejs/vitepress/issues/1265",0.8107064,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRUXiik-Cs4nPirc5jMIwj9F97x-x5EJNg6fYj2HC1Es":-1},"/vuejs/vitepress/753"]