\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.",[2865,2868],{"name":2866,"color":2867},"need more info","bdbefc",{"name":2869,"color":2870},"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.71333313,{"description":2880,"labels":2881,"number":2883,"owner":2872,"repository":2873,"state":2874,"title":2884,"updated_at":2885,"url":2886,"score":2887},"### Describe the bug\r\n\r\nHi,\r\n\r\nI'm currently working on a project where I'd like to proceed with building despite any dead links or missing resources. While I understand that it's best practice to have a documentation without these issues, I believe it's more important to generate a build even with potential inconsistencies.\r\n\r\nI enabled the option ```ignoreDeadLinks: true``` but I am not able to build.\r\n\r\nIt complains about a ```productUnit.png``` file which is missing indeed, but I would like to build anyway.\r\n\r\nHow can I achieve this?\r\n\r\nAs a side note, I typically keep my assets such as images, spreadsheets, and PDFs in the same folder as my markdown files.\r\n\r\nRegards,\r\n\r\nFabiano\r\n\r\n```js\r\n⠼ building client + server bundles...Could not resolve \"./productUnit.png\" from \"src/app/catalog/product/productUnit.md\"\r\nfile: /opt/zen.erp.docs.engine/src/app/catalog/product/productUnit.md\r\n✖ building client + server bundles...\r\nbuild error:\r\nRollupError: Could not resolve \"./productUnit.png\" from \"src/app/catalog/product/productUnit.md\"\r\n at error (file:///opt/zen.erp.docs.engine/node_modules/rollup/dist/es/shared/node-entry.js:2287:30)\r\n at ModuleLoader.handleInvalidResolvedId (file:///opt/zen.erp.docs.engine/node_modules/rollup/dist/es/shared/node-entry.js:24860:24)\r\n at file:///opt/zen.erp.docs.engine/node_modules/rollup/dist/es/shared/node-entry.js:24822:26\r\n```\r\n\r\n### Reproduction\r\n\r\nCould not reproduce in stackblitz:\r\n\r\nhttps://stackblitz.com/edit/vite-vzvbjb?file=docs%2F.vitepress%2Fconfig.ts\r\n\r\n### Expected behavior\r\n\r\nTo build the docs\r\n\r\n### System Info\r\n\r\n```Text\r\nvitepress 1.0.0-rc.20\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.",[2882],{"name":2869,"color":2870},3081,"Can't build when files are missing (ignoreDeadLinks is not working)","2023-11-25T08:11:59Z","https://github.com/vuejs/vitepress/issues/3081",0.74871635,{"description":2889,"labels":2890,"number":2894,"owner":2872,"repository":2873,"state":2895,"title":2896,"updated_at":2897,"url":2898,"score":2899},"### 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.",[2891],{"name":2892,"color":2893},"bug: pending triage","e99695",2556,"closed","页面与首页重合","2023-07-07T00:04:41Z","https://github.com/vuejs/vitepress/issues/2556",0.6701179,{"description":2901,"labels":2902,"number":2903,"owner":2872,"repository":2873,"state":2895,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Is your feature request related to a problem? Please describe.\n\n\r\n(The Home Page)\r\n\r\n\r\n(The Download Page)\r\n\r\nbut, the style:\r\n```\r\n --vp-home-hero-image-background-image: linear-gradient(\r\n -45deg,\r\n #186068 50%,\r\n #00e5ff 50%\r\n );\r\n```\r\nConflict with the \"Download\" page (i.e. Download does not require this style, but the home page does)\r\n\r\n\n\n### Describe the solution you'd like\n\nAdd image2? It means defining some content as images, and the content can be changed through style.css\n\n### Describe alternatives you've considered\n\nAdd the following code to \"/download/index. md\":\r\n\r\n```\r\n\u003Cstyle moudle>\r\n:root {\r\n --vp-home-hero-image-background-image: none;\r\n}\r\n\u003C/style>\r\n```\r\nBut it was found that this string of code may affect home (whether it is\u003Cstyle>,\u003Cstyle module>, or\u003Cstyle scoped>)\r\n\r\nMaybe it's a problem with my server?\n\n### Additional context\n\nhome page:\r\n```\r\n---\r\n# https://vitepress.dev/reference/default-theme-home-page\r\nlayout: home\r\n\r\nhero:\r\n name: \"Cr-DGC\"\r\n text: \"不纯粹的石榴石晶体\"\r\n tagline: 基于Minecraft原版制作的PBR材质包\r\n image: \r\n src: \"/images/home_logo.png\"\r\n actions:\r\n - theme: brand\r\n text: Get Start\r\n link: /docs/\r\n - theme: alt\r\n text: Download\r\n link: /download/\r\n\r\nfeatures:\r\n - title: XXX\r\n details:XXX\r\n - title: XXX\r\n details: XXX\r\n - title: XXX\r\n details: XXX\r\n---\r\n\r\n```\r\n\r\nDownload Page:\r\n\r\n```\r\n\r\n---\r\nlayout: home\r\nprev: false\r\nnext: false\r\nsidebar: false\r\n\r\nhero:\r\n name: \"Cr-DGC\"\r\n text: \"不纯粹的石榴石晶体\"\r\n tagline: 基于Minecraft原版制作的PBR材质包\r\n image: \r\n src: \"/images/home_logo.png\"\r\n actions:\r\n - theme: brand\r\n text: 下载开源版本\r\n link: /docs/\r\n - theme: alt\r\n text: 下载赞助版本\r\n link: /download/\r\n\r\n---\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.",[],3681,"Set like \"images2\"","2024-04-28T12:25:29Z","https://github.com/vuejs/vitepress/issues/3681",0.68262726,{"description":2909,"labels":2910,"number":2912,"owner":2872,"repository":2873,"state":2895,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Describe the bug\n\ndata.posts does not get read properly\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/kfung21/test-blog\n\n### Expected behavior\n\nshow blog posts\n\n### System Info\n\n```Text\n[ERROR] \"vitepress\" resolved to an ESM file. ESM file cannot be loaded by `require`. See https://vitejs.dev/guide/troubleshooting.html#this-package-is-esm-only for more details. [plugin externalize-deps]\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.",[2911],{"name":2892,"color":2893},3655,"createContentLoader data.posts.js resolved to an ESM file and cannot be loaded by require. 1.0.0-rc.45","2024-03-22T00:04:27Z","https://github.com/vuejs/vitepress/issues/3655",0.6862713,{"description":2918,"labels":2919,"number":2922,"owner":2872,"repository":2873,"state":2895,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### 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.",[2920,2921],{"name":2892,"color":2893},{"name":2869,"color":2870},2981,"Setting base path doesn't set logo path","2024-01-29T00:04:27Z","https://github.com/vuejs/vitepress/issues/2981",0.6958323,{"description":2928,"labels":2929,"number":2931,"owner":2872,"repository":2873,"state":2895,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Describe the bug\r\n\r\nI have a npm package called @declarative-gridstacks/react, it exports a bunch of react components (compiled with babel-loader obviously), I import these modules use them in vitepress it words good in dev mode... But when I actually try to build the vitepress project, it doesn't build.\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\n```jsx\r\nimport {\r\n GridstackContainer,\r\n} from \"@declarative-gridstack/react\"; // This is in node_modules.\r\n\r\nconst Component = () => {\r\nreturn \u003CGridstackContainer />\r\n}\r\n\r\nexport default Component;\r\n```\r\n\r\n// Import this code in \r\n```vue\r\n\u003Cdiv ref=\"el\" />\r\n\r\n\u003Cscript setup>\r\nimport { createElement } from 'react'\r\nimport { createRoot } from 'react-dom/client'\r\nimport { ref, onMounted } from 'vue'\r\nimport Simple from '../components/simple/Simple.jsx'\r\n\r\nconst el = ref()\r\nonMounted(() => {\r\n const root = createRoot(el.value)\r\n root.render(createElement(Simple, {}, null))\r\n})\r\n\u003C/script>\r\n```\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nThe project should build... It works fine in dev mode...\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: macOS 12.5\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 1.16 GB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.20.1 - ~/.nvm/versions/node/v16.20.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v16.20.1/bin/yarn\r\n npm: 8.19.4 - ~/.nvm/versions/node/v16.20.1/bin/npm\r\n Browsers:\r\n Chrome: 115.0.5790.114\r\n Safari: 15.6\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.",[2930],{"name":2892,"color":2893},2709,"Unable to build the docs project when importing a module from node_modules","2023-08-07T00:04:27Z","https://github.com/vuejs/vitepress/issues/2709",0.70105845,{"description":2937,"labels":2938,"number":2942,"owner":2872,"repository":2873,"state":2895,"title":2943,"updated_at":2944,"url":2945,"score":2946},"> @brc-dd \r\n> \r\n> ```ts\r\n> import { defineConfig } from 'vitepress';\r\n> \r\n> export default defineConfig({\r\n> transformPageData(pageData) {\r\n> return {\r\n> frontmatter: {\r\n> ...pageData.frontmatter,\r\n> head: [\r\n> [\r\n> 'script',\r\n> { type: 'application/ld+json' },\r\n> pageData.relativePath === 'index.md'\r\n> ```\r\n\r\nWhen I using Dynamic Routes. To uniformly manage and generate pages with a consistent structure, which involves changing the `header` [#2516](https:github.com/vuejs/vitepress/discussions/2516), the suggestion is also to use `.vitepress/config.js` to use `transformPageData`\r\n\r\nI was wondering if `transformPageData` would be in Dynamic Routes configure `[pkg].paths.js`. Avoid me adding too much judgment in `.vitepress/config.js`, and managing it in only one place.\r\n\r\n```\r\n.\r\n└─ packages\r\n ├─ [pkg].md # route template\r\n └─ [pkg].paths.js # route paths loader\r\n```\r\n\r\n```js\r\n// packages/[pkg].paths.js\r\nexport default {\r\n paths() {\r\n return [\r\n { params: { pkg: 'foo' }},\r\n { params: { pkg: 'bar' }}\r\n ]\r\n },\r\n transformPageData(pageData) {\r\n // ...\r\n }\r\n}\r\n```\r\n\r\n_Originally posted by @Zhengqbbb in https://github.com/vuejs/vitepress/issues/883#issuecomment-1614242193_\r\n ",[2939],{"name":2940,"color":2941},"build","377ba8",2726,"transformPageData from dynamic paths","2023-08-11T00:04:17Z","https://github.com/vuejs/vitepress/issues/2726",0.70201063,{"description":2948,"labels":2949,"number":2951,"owner":2872,"repository":2873,"state":2895,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Is your feature request related to a problem? Please describe.\r\n\r\nCan the Type.js plugin be built-in to make the homepage look better, or can an entrance be added for developers to run custom JS files for some custom operations\r\n\r\n### Describe the solution you'd like\r\n\r\n[See this doc](https://steven.codes/typerjs/)\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.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.",[2950],{"name":2869,"color":2870},4086,"Support more plugins","2025-03-08T04:41:54Z","https://github.com/vuejs/vitepress/issues/4086",0.7190203,{"description":2957,"labels":2958,"number":2959,"owner":2872,"repository":2873,"state":2895,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### 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.72106034,["Reactive",2965],{},["Set"],["ShallowReactive",2968],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$favNWTB5FygNJ7GXdHIdcNfwhsahSPuduGwRcQ-2lhCE":-1},"/vuejs/vitepress/2815"]