\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.",[3040,3043],{"name":3041,"color":3042},"need more info","bdbefc",{"name":3027,"color":3028},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.76710624,{"description":3050,"labels":3051,"number":3055,"owner":3030,"repository":3031,"state":3056,"title":3057,"updated_at":3058,"url":3059,"score":3060},"### Describe the bug\n\n\r\n复现方式,在服务器部署后,访问具体的某一个子菜单后,鼠标选中浏览器地址,按下enter键。就会导致如图效果,首页会和选中页面重合\n\n### Reproduction\n\n在服务器部署后,访问具体的某一个子菜单后,鼠标选中浏览器地址,按下enter键\r\n例如 :\r\n我已经定位到这个具体的菜单 : http://127.0.0.1:80/demo/specify01\r\n\r\n当我在浏览器地址栏使用鼠标选中地址栏并且按下enter键的时候,就会出现上面的情况\n\n### Expected behavior\n\n我希望我在定位到具体的菜单后,在浏览器快速访问时,会帮我定位到具体的菜单,而不是和首页重合\n\n### System Info\n\n```sh\n1.0.0-beta.3\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.",[3052],{"name":3053,"color":3054},"bug: pending triage","e99695",2556,"closed","页面与首页重合","2023-07-07T00:04:41Z","https://github.com/vuejs/vitepress/issues/2556",0.7110941,{"description":3062,"labels":3063,"number":3066,"owner":3030,"repository":3031,"state":3056,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Describe the bug\r\n\r\nSetting the base path on GitHub pages does not update the path for logo\r\n\r\n### Reproduction\r\n\r\n1. Create a new app\r\n2. Set the `base` path to something eg: `/hello/`\r\n3. Set your logo to `/logo.\u003Cext>`\r\n\r\nHere is what I have - https://github.com/akshaybabloo/dotfiles/tree/main/docs\r\n\r\n### Expected behavior\r\n\r\nThe path after generation should be `\u003Culr>/hello/logo.\u003Cext>` but it generates `\u003Curl>/logo.\u003Cext>`\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 6.2 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)\r\n CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz\r\n Memory: 18.87 GB / 31.07 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 20.5.1 - ~/.nvm/versions/node/v20.5.1/bin/node\r\n Yarn: 1.22.19 - ~/.npm-global/bin/yarn\r\n npm: 9.8.0 - ~/.nvm/versions/node/v20.5.1/bin/npm\r\n Browsers:\r\n Brave Browser: 117.1.58.127\r\n Chrome: 117.0.5938.88\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.12 => 1.0.0-rc.14\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI am using Bun as my package manager.\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.",[3064,3065],{"name":3053,"color":3054},{"name":3027,"color":3028},2981,"Setting base path doesn't set logo path","2024-01-29T00:04:27Z","https://github.com/vuejs/vitepress/issues/2981",0.7245696,{"description":3072,"labels":3073,"number":3081,"owner":3030,"repository":3031,"state":3056,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Is your feature request related to a problem? Please describe.\n\n Hi team, currently there is no `StackOverlfow` icon in the `SocialLinkIcon` type, which makes it difficult for the developers to add their relevant StackOverflow links to their documentation sites.\n\n### Describe the solution you'd like\n\nAdd the `StackOverflow` icon to the `SocialLinkIcon` type,.\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.",[3074,3077,3080],{"name":3075,"color":3076},"theme","0754FB",{"name":3078,"color":3079},"has-workaround","1B4515",{"name":3027,"color":3028},4135,"Add `StackOverflow` icon to the `SocialLinkIcon` type.","2024-11-12T04:43:09Z","https://github.com/vuejs/vitepress/issues/4135",0.74400014,{"description":3087,"labels":3088,"number":3089,"owner":3030,"repository":3031,"state":3056,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Is your feature request related to a problem? Please describe.\n\n你好,我在md文件引入了自己的vue组件,但外层有一个.vp-doc元素自带的一堆样式总是会影响到自己开发的组件样式,这种情况该如果解决?\n\n### Describe the solution you'd like\n\n\r\n比如ezlist 引入了tabel,那就会受到.vp-doc的这行影响,从而改变布局\r\n.vp-doc table {\r\n display: block;\r\n border-collapse: collapse;\r\n margin: 20px 0;\r\n overflow-x: auto;\r\n}\r\n\r\n# list.md 文件\r\n\u003CEzList>\u003C/Ezlist>\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.",[],2551,"自己定义的vue组件总是受到外层.vp-doc样式影响","2023-09-02T00:04:13Z","https://github.com/vuejs/vitepress/issues/2551",0.74444914,{"description":3095,"labels":3096,"number":3098,"owner":3030,"repository":3031,"state":3056,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Describe the bug\n\n- building client + server bundles...Could not resolve './_media/ArrayList-inherit.jpg' from docs\\java\\Java基础入门\\类和实例.md\r\n✖ building client + server bundles...\r\nCould not resolve './_media/ArrayList-inherit.jpg' from docs\\java\\Java基础入门\\类和实例.md (x2)\n\n### Reproduction\n\n# markdown file path\r\ndocs/java/Java基础入门/类和实例.md\r\n\r\n# image file path\r\ndocs/java/Java基础入门/_media/ArrayList-inherit.jpg\r\n\r\n# in markdown file using\r\n``\r\n\r\nor \r\n\r\n``\r\n\r\n# then, run `yarn docs:build` building\r\ncompile error and failed\r\n```text\r\n- building client + server bundles...Could not resolve './_media/ArrayList-inherit.jpg' from docs\\java\\Java基础入门\\类和实例.md\r\n✖ building client + server bundles...\r\nCould not resolve './_media/ArrayList-inherit.jpg' from docs\\java\\Java基础入门\\类和实例.md (x2)\r\n```\r\n\r\n# other information\r\nwhen use `\u003Cimg :src=\"$withBase('./_media/ArrayList-inherit.jpg')\" alt=\"ArrayList类继承关系\" />` , no errors.\n\n### Expected behavior\n\nno errors, compile success\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz\r\n Memory: 16.46 GB / 31.85 GB\r\n Binaries:\r\n Node: 14.18.2 - E:\\apps\\node-v14\\node.EXE\r\n Yarn: 1.22.10 - E:\\apps\\node-v14\\node_global\\yarn.CMD\r\n npm: 7.20.0 - E:\\apps\\node-v14\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (98.0.1108.50)\r\n Internet Explorer: 11.0.19041.1202\r\n npmPackages:\r\n vitepress: ^0.22.2 => 0.22.2\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\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.",[3097],{"name":3041,"color":3042},534,"in markdown file, use image file, image file exists and path correct, but image load failed","2023-01-21T14:34:14Z","https://github.com/vuejs/vitepress/issues/534",0.7550255,{"description":3104,"labels":3105,"number":3107,"owner":3030,"repository":3031,"state":3056,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Describe the bug\n\nI was trying to follow these instructions [here](https://vitepress.dev/guide/extending-default-theme#customizing-css) just to change the color of the Title on the home page.\r\nAccording [this section](https://vitepress.dev/guide/custom-theme#theme-resolving), just by creating the `.vitepress/theme/index.js` and `.vitepress/theme/custom.css` files that the [Customizing CSS](https://vitepress.dev/guide/extending-default-theme#customizing-css) suggests should be enough to have it being read.\r\nBut no. That alone does not work.\r\n\r\nI had to add `import './theme/custom.css'` to the `config.ts` file first to force it to read the custom css.\r\n\r\n**edit:**\r\nmore recently I tried renaming the `.vitepress/theme/index.js` to `.ts` and then it woke up! now it is aware of that file...\r\nLooks like a bug, no?\n\n### Reproduction\n\nI was trying to follow these instructions [here](https://vitepress.dev/guide/extending-default-theme#customizing-css) just to change the color of the Title on the home page.\r\nAccording [this section](https://vitepress.dev/guide/custom-theme#theme-resolving), just by creating the `.vitepress/theme/index.js` and `.vitepress/theme/custom.css` files that the [Customizing CSS](https://vitepress.dev/guide/extending-default-theme#customizing-css) suggests should be enough to have it being read.\r\nBut no. That alone does not work.\r\n\r\nI had to add `import './theme/custom.css'` to the `config.ts` file first to force it to read the custom css.\r\n\r\n**edit:**\r\nmore recently I tried renaming the `.vitepress/theme/index.js` to `.ts` and then it woke up! now it is aware of that file...\r\nLooks like a bug, no?\n\n### Expected behavior\n\nbe able to follow along the initial instructions on custom css\n\n### System Info\n\n```sh\nmac os catalina latest vitepress nodejs 16 npm 6.9\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.",[3106],{"name":3053,"color":3054},2612,"simple css overriding ain't happening","2023-08-21T00:04:12Z","https://github.com/vuejs/vitepress/issues/2612",0.7568281,{"description":3113,"labels":3114,"number":3115,"owner":3030,"repository":3031,"state":3056,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Is your feature request related to a problem? Please describe.\n\nno\n\n### Describe the solution you'd like\n\nTake https://abc.com/tutorial/ as an example: \r\n\r\n- if there is an \"index.md\", https://abc.com/tutorial/ is ok.\r\n\r\n- but https://abc.com/tutorial is 404\r\n\r\nCan we let https://abc.com/tutorial redirect to https://abc.com/tutorial/ by default.\r\n\r\nThanks.\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.",[],3788,"fix directory 404","2024-04-28T12:24:48Z","https://github.com/vuejs/vitepress/issues/3788",0.76080424,{"description":3121,"labels":3122,"number":3126,"owner":3030,"repository":3031,"state":3056,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Is your feature request related to a problem? Please describe.\n\nHi, \r\n\r\nMy Vitepress site is still under local development, and I am trying to figure out how to use [DecapCMS](https://decapcms.org/) with Vitepress in my local development setup.\r\n\r\nDecapCMS [has two ways of installation](https://decapcms.org/docs/add-to-your-site/): One is using an HTML file with a CDN script, and another is via their NPM package. \r\n\r\nI tried both, and it does not work. For example, I created an admin folder at the root level with their index.html and config.yml files and tried to access the admin path from the local dev server, but it threw a 404 error.\r\n\r\nWhat do you think the best way is to do this? I appreciate any help or guidance you can give me on this.\r\n\r\nP.S: I have gone through the docs related to [connecting a CMS with Vitepress](https://vitepress.dev/guide/cms), but I could not figure out how to use that to setup DecapCMS with Vitepress.\r\n\r\nThanks!\n\n### Describe the solution you'd like\n\nClear instructions on how to use DecapCMS with Vitepress.\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.",[3123],{"name":3124,"color":3125},"question","5D5FAE",2651,"How to integrate Vitepress with DecapCMS (Formerly known as NetlifyCMS)","2023-07-19T06:52:01Z","https://github.com/vuejs/vitepress/issues/2651",0.7612336,["Reactive",3132],{},["Set"],["ShallowReactive",3135],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkAvIQnjSZ3OT8WSUAtmQG-t6mE5dJkWGtlNc3PXVdio":-1},"/vuejs/vitepress/2405"]