\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.",[3028,3031],{"name":3029,"color":3030},"need more info","bdbefc",{"name":3032,"color":3033},"stale","ededed",3292,"vuejs","vitepress","open","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.8067119,{"description":3043,"labels":3044,"number":3049,"owner":3035,"repository":3036,"state":3037,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### Is your feature request related to a problem? Please describe.\n\nI noticed that the search bar by default is pretty bad compared to the one in mkdocs, at least for me\r\n\n\n### Describe the solution you'd like\n\nadd lunr.js which has proven to be very good in conjunction with mkdocs and you hardly need to configure it extensively to get a good result\r\nhttps://github.com/olivernn/lunr.js\n\n### Describe alternatives you've considered\n\nimprove default search\n\n### Additional context\n\nVitepress:\r\nthe desired result always appears last\r\n\r\n\r\nMkDocs:\r\n\r\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.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.",[3045,3048],{"name":3046,"color":3047},"has-workaround","1B4515",{"name":3032,"color":3033},3429,"Add lunr.js as one of the available plugins for Search","2024-03-07T11:19:10Z","https://github.com/vuejs/vitepress/issues/3429",0.8223482,{"description":3055,"labels":3056,"number":3061,"owner":3035,"repository":3036,"state":3037,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### Is your feature request related to a problem? Please describe.\r\n\r\nSupport syntax highlight on inline code in docs.\r\n\r\nThe picture below is from an HTML code snippet using Prism and a syntax like this:\r\n```html\r\n\u003Ccode class=\"language-js\">if (user.actionsHistory[0].type ===\"undo\")\u003C/code>\r\n```\r\n\r\n\r\n\r\n\r\nAnd the picture below is the same writing with Vitepress:\r\n```md\r\n`if (user.actionsHistory.at(-1).type ===\"undo\")`\r\n```\r\n\r\n\r\n\r\n\r\nAs you see the Syntax Highlighting is gone. Could be cool to have an automatic inline Syntax Highlighting for md docs.\r\n\r\nHere is another example for a CSS code snippet. On the left using markdown and viteperss, and on the right, using html and prism:\r\n\r\n\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nThere'v been some suggestions before on vitepress: https://github.com/vuejs/vitepress/issues/1343 and vuepress: https://github.com/vuejs/vuepress/issues/1212 on how the syntax could look like. I personally do not have a preference. But I believe this syntax:\r\n```md\r\nAnd `if (someCondition === true)`{lang=js}\r\n```\r\nallows for future expansions:\r\n```md\r\nAnd `if (someCondition === true)`{lang=js,someFlag=false,someOtherFlag=true}\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\nHave not tried anything yet. Just faced this requirement while trying out vitepress. If I ever came up with a solution that did or did not work will share here.\r\n\r\n### Additional context\r\n\r\nThere was already 1 issue about this: https://github.com/vuejs/vitepress/issues/1343, but was closed as \"Not seeing any demand for this\". So I re-created this issue as a demand.\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.",[3057,3060],{"name":3058,"color":3059},"theme","0754FB",{"name":3032,"color":3033},3093,"Feature Request: Inline Syntax Highlight","2025-03-02T18:10:32Z","https://github.com/vuejs/vitepress/issues/3093",0.8237354,{"description":3067,"labels":3068,"number":3070,"owner":3035,"repository":3036,"state":3071,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### Is your feature request related to a problem? Please describe.\r\n\r\nCurrently only emojis are supported in the features section in home layout, which is already great, but there are a lot of cases where a custom image would be a better fit.\r\n\r\nOpen discussion\r\nhttps://github.com/vuejs/vitepress/discussions/1589#discussioncomment-4415494\r\n\r\n### Describe the solution you'd like\r\n\r\n```\r\n features:\r\n - icon: [LINK TO SVG IMAGE]\r\n title: my title\r\n details: my details\r\n link: https://github.com/vuejs/vitepress\r\n linkText: Let's jump right in\r\n```\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/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.vuejs.org).\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.",[3069],{"name":3058,"color":3059},1702,"closed","Support svg images in the features section in home layout","2023-01-21T14:17:01Z","https://github.com/vuejs/vitepress/issues/1702",0.7657041,{"description":3077,"labels":3078,"number":3079,"owner":3035,"repository":3036,"state":3071,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Is your feature request related to a problem? Please describe.\r\n\r\nI would like to automatically add a section to every single page, but also have it appear in the outline, and for it to have an id, snap to element link, etc... automatically generated. I would also like it to appear before the \"last updated\" and \"edit in github links.\"\r\n\r\n### Describe the solution you'd like\r\n\r\nAn option `transformMarkdown`, just like `transformHtml`, that is called directly before rendering instead of directly afterward.\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nIf it might help this move forward faster, I would be willing to write a PR.\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.vuejs.org).\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.",[],1955,"`transformMarkdown` config option","2023-03-18T00:04:17Z","https://github.com/vuejs/vitepress/issues/1955",0.78018135,{"description":3085,"labels":3086,"number":3087,"owner":3035,"repository":3036,"state":3071,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Is your feature request related to a problem? Please describe.\n\n`mainEntryPointFilePath` only allows a single entrypoint.\r\n\r\nLet's say I have a repo that has multiple exports and types:\r\n```\r\n\"exports\": {\r\n \".\": \"./dist/index.js\",\r\n \"./foo\": \"./dist/foo/foo.js\",\r\n \"./util\": \"./dist/util/index.js\"\r\n },\r\n \"typesVersions\": {\r\n \"*\": {\r\n \"*\": [\r\n \"dist/types/src/index.d.ts\"\r\n ],\r\n \"foo\": [\r\n \"dist/types/src/foo/index.d.ts\"\r\n ],\r\n \"util\": [\r\n \"dist/types/src/util/index.d.ts\"\r\n ]\r\n }\r\n },\r\n```\r\n\r\nI can't generate correct docs based on this. The only thing you can do is export all types at the root, but that is incorrect for this project structure.\n\n### Describe the solution you'd like\n\nAllow multiple entrypoints that reflects the setup of the repo.\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.",[],1077,"Allow multiple entrypoints","2023-01-21T14:30:04Z","https://github.com/vuejs/vitepress/issues/1077",0.79677784,{"description":3093,"labels":3094,"number":3098,"owner":3035,"repository":3036,"state":3071,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Describe the bug\r\n\r\nHero image don't bind after deployment If place logo.png to /images it does not work.\r\nThis image does not compile to the assets and on real site can't get image.Please fix\r\n\r\n### Reproduction\r\n\r\nSet hero section\r\nSet image:\r\n src: logo.png\r\n\r\n### Expected behavior\r\n\r\nShould can place logo(any images) to images directory\r\n\r\n### System Info\r\n\r\n```Text\r\nafter deploy\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.",[3095],{"name":3096,"color":3097},"bug: pending triage","e99695",3813,"Hero section image error","2024-04-28T12:24:41Z","https://github.com/vuejs/vitepress/issues/3813",0.8070528,{"description":3104,"labels":3105,"number":3107,"owner":3035,"repository":3036,"state":3071,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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.",[3106],{"name":3046,"color":3047},2878,"feat: build dry run or verify option","2023-09-08T00:04:10Z","https://github.com/vuejs/vitepress/issues/2878",0.80752814,{"description":3113,"labels":3114,"number":3115,"owner":3035,"repository":3036,"state":3071,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Is your feature request related to a problem? Please describe.\n\nI've embed a video in my markdown by search the help of Typora.\r\nIt works fine in Typora.\r\nIt is like this in my markdown:\r\n```\r\n\u003Cvideo controls=\"controls\" src=\"在家办公指南.assets\\Video_2020-02-23_230241.mp4\" />\r\n```\r\nIt works fine with the localhost via the command ` yarn docs:dev`\r\nbut when `yarn docs:build`, I got an error.\r\nHow can I do?\n\n### Describe the solution you'd like\n\nSupport the video control.\r\n\r\nI set up the site in LAN and won't expose to the WAN, the storage is no problem.\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.",[],1477,"embed video in markdown with vitepress","2023-01-21T14:25:05Z","https://github.com/vuejs/vitepress/issues/1477",0.8146376,{"description":3121,"labels":3122,"number":3124,"owner":3035,"repository":3036,"state":3071,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Describe the bug\n\nBuild failed\n\n### Reproduction\n\nclone [vitepress-template](https://github.com/Tyh2001/vitepress-template)\r\n\r\n```shell\r\npnpm i\r\n\r\npnpm build\r\n```\r\n\r\nI'm not sure if the mistake is `vitepress` or [fighting-design](https://github.com/FightingDesign/fighting-design)\r\n\r\nerr message:\r\n\r\n```shell\r\n> vitepress-template@ build D:\\项目-我的\\vitepress-template\r\n D:\\项目-我的\\vitepress-template\\node_modules\\.pnpm\\fighting-design@0.8.0-alpha.5\\node_modules\\fighting-design\\es\\index.js:1 \r\nimport \"./index2.js\";\r\n^^^^^^\r\n\r\nSyntaxError: Cannot use import statement outside a module\r\n at Object.compileFunction (node:vm:352:18)\r\n at wrapSafe (node:internal/modules/cjs/loader:1033:15)\r\n at Module._compile (node:internal/modules/cjs/loader:1069:27)\r\n at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)\r\n at Module.load (node:internal/modules/cjs/loader:981:32)\r\n at Function.Module._load (node:internal/modules/cjs/loader:822:12)\r\n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/translators:170:29)\r\n at ModuleJob.run (node:internal/modules/esm/module_job:198:25)\r\n at async Promise.all (index 0)\r\n at async ESMLoader.import (node:internal/modules/esm/loader:385:24)\r\n ELIFECYCLE Command failed with exit code 1.\r\n```\r\n\n\n### Expected behavior\n\nBuild successful\n\n### System Info\n\n```shell\n\"vitepress\": \"1.0.0-alpha.27\",\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.",[3123],{"name":3096,"color":3097},1579,"Build error","2023-01-21T14:20:51Z","https://github.com/vuejs/vitepress/issues/1579",0.8151566,["Reactive",3130],{},["Set"],["ShallowReactive",3133],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyk0r_1AMnpJzvV684C7GOQsZsfh55eylVac27L6lNYE":-1},"/vuejs/vitepress/1660"]