\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.",[2882,2885],{"name":2883,"color":2884},"need more info","bdbefc",{"name":2869,"color":2870},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.7801032,{"description":2892,"labels":2893,"number":2895,"owner":2872,"repository":2873,"state":2874,"title":2896,"updated_at":2897,"url":2898,"score":2899},"### Describe the bug\n\nWhen I hide the navbar (parameter \"navbar: false\") it works correctly on normal browser navigation, but when I print a page something is wrong.\r\n\r\nOn the printed page the navbar is not hide and is shown with the text \"Return to top\" inside.\n\n### Reproduction\n\nCreate a new vitepress project.\r\n\r\nIn the index.md file, write the following code:\r\n```md\r\n---\r\nnavbar: false\r\n---\r\n\r\n# Hello\r\n```\r\n\r\nRun vitepress dev, brose to the site, call print (Ctrl + P) and print the page or save as pdf.\n\n### Expected behavior\n\nThe navbar must be hide also on pdf.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 12.6.9\r\n CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz\r\n Memory: 34.23 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.18.1 - ~/.nvm/versions/node/v18.18.1/bin/node\r\n npm: 9.8.1 - ~/.nvm/versions/node/v18.18.1/bin/npm\r\n Browsers:\r\n Chrome: 118.0.5993.70\r\n Safari: 16.6\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.21 => 1.0.0-rc.21\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.",[2894],{"name":2869,"color":2870},3086,"Navbar visible on print when navbar param equals false","2025-03-02T18:10:33Z","https://github.com/vuejs/vitepress/issues/3086",0.78025347,{"description":2901,"labels":2902,"number":2907,"owner":2872,"repository":2873,"state":2874,"title":2908,"updated_at":2909,"url":2910,"score":2911},"In general we have something that looks like:\r\n\r\n[bonito.md]\r\n```\r\nSome text could be here as well\r\n\r\n\u003Cdiv>\r\n \u003Cdiv class=\"bonito-fragment\" id=\"b240e6cb-b8c0-4d12-8af1-b509dcc29e55\" data-jscall-id=\"root\">\r\n \u003Cdiv>\r\n \u003Cscript src=\"bonito/js/Bonito.bundled.js\" type=\"module\">\u003C/script>\r\n \u003Cstyle>\u003C/style>\r\n \u003Cdiv>\u003C/div>\r\n \u003C/div>\r\n \u003Cdiv>\r\n \u003Cscript type=\"module\">Bonito.lock_loading(() => Bonito.init_session('b240e6cb-b8c0-4d12-8af1-b509dcc29e55', null, 'root'))\u003C/script>\r\n \u003Cspan>\u003C/span>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003Cdiv class=\"bonito-fragment\" id=\"d9c84005-2c6f-46b8-be1a-92ee56eea191\" data-jscall-id=\"subsession-application-dom\">\r\n \u003Cdiv>\r\n \u003Cstyle>\u003C/style>\r\n \u003Cdiv>\u003C/div>\r\n \u003C/div>\r\n \u003Cdiv>\r\n \u003Cscript type=\"module\"> Bonito.lock_loading(() => {\r\n return Bonito.fetch_binary('bonito/bin/c3e2dbd67f62c4fc1ead4bd004e119b63393e0ff-5683387923680860656.bin').then(msgs=> Bonito.init_session('d9c84005-2c6f-46b8-be1a-92ee56eea191', msgs, 'sub'));\r\n })\r\n\u003C/script>\r\n \u003Cdiv style=\"width: 100%; height: 100%\" data-jscall-id=\"1\">\r\n \u003Ccanvas style=\"display: block\" data-jscall-id=\"2\" tabindex=\"0\">\u003C/canvas>\r\n \u003C/div>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/div>\r\n```\r\nA simplified version (reproducer) with source files can be found here: https://github.com/lazarusA/TemplateDocsVitePress.jl/tree/master/md_srcs\r\n\r\nwhere the issue happens for the `bonito.md` file. Any advice or suggestions? This is suppose to be use to generate potentially many interactive plots, hence having a general approach would be nice.\r\n\r\nShould we just parse it as raw html? does it make sense...\r\n\r\n_Originally posted by @lazarusA in https://github.com/vuejs/vitepress/discussions/3909_",[2903,2906],{"name":2904,"color":2905},"build","377ba8",{"name":2869,"color":2870},3910,"support for \u003Cscript src=\"...\" type=\"module\">\u003C/script> and \u003Cstyle>\u003C/style> ","2025-03-02T18:09:04Z","https://github.com/vuejs/vitepress/issues/3910",0.79555273,{"description":2913,"labels":2914,"number":2917,"owner":2872,"repository":2873,"state":2874,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Is your feature request related to a problem? Please describe.\n\nWhenever I execute pnpm docs:build, I always fail to package successfully and get an error ReferenceError: document is not defined.\n\n### Describe the solution you'd like\n\ndocs system is built successfully! No error is reported when executing pnpm docs:build. And a successful dist package is packaged.\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\ngithub : https://github.com/Hollelihanqi/qh-ui.git\r\n/** @type {import('vitepress').Theme} */\r\n\r\nimport { h } from \"vue\";\r\nimport VPApp, { NotFound, globals } from \"../vitepress\";\r\nimport DefaultTheme from \"vitepress/theme\";\r\n// import { define } from '../utils/types'\r\n\r\n// import 'uno.css'\r\nimport \"virtual:uno.css\";\r\nimport './style.css'\r\n\r\nimport \"../vitepress/styles/base.scss\";\r\n\r\nimport ElementPlus from \"element-plus\";\r\nimport \"element-plus/dist/index.css\";\r\nimport YtoUplus from '@yto/custom'\r\nimport '@yto/custom/index.css'\r\n\r\n// import type { Theme } from 'vitepress'\r\nexport default {\r\n extends: DefaultTheme,\r\n NotFound,\r\n Layout: VPApp,\r\n async enhanceApp({ app }) {\r\n globals.forEach(([name, Comp]) => {\r\n app.component(name, Comp);\r\n });\r\n app.use(ElementPlus);\r\n app.use(YtoUplus);\r\n // @ts-ignore\r\n // if (!import.meta.env.SSR) {\r\n // const custom = await import('@yto/custom').then((m) => m)\r\n // app.use(custom.default)\r\n // }\r\n },\r\n // Layout() {\r\n // return h(DefaultTheme.Layout, null, {\r\n // \"aside-outline-before\": () => h(\"div\", {}, \"我是前置内容\"),\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.",[2915,2916],{"name":2883,"color":2884},{"name":2869,"color":2870},4269,"Build error: ReferenceError: document is not defined","2025-03-02T18:08:24Z","https://github.com/vuejs/vitepress/issues/4269",0.80289936,{"description":2923,"labels":2924,"number":2929,"owner":2872,"repository":2873,"state":2930,"title":2931,"updated_at":2932,"url":2933,"score":2934},"Currently there are lot of repeated icons in generated dist/**/*.html files. Those can be avoided by these.",[2925,2926],{"name":2869,"color":2870},{"name":2927,"color":2928},"perf","378A61",3399,"closed","Switch to CSS icons or SVG sprites","2024-02-25T00:05:04Z","https://github.com/vuejs/vitepress/issues/3399",0.7434301,{"description":2936,"labels":2937,"number":2941,"owner":2872,"repository":2873,"state":2930,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Is your feature request related to a problem? Please describe.\n\nThe problem I'm having is targeting specific Markdown pages with CSS\n\n### Describe the solution you'd like\n\nLike VuePress (v1 and v2), it has `pageClass`, enabling very easy page targeting with CSS\r\nI couldn't find anything of this sort in VitePress\r\n\r\nhttps://v2.vuepress.vuejs.org/reference/default-theme/frontmatter.html#pageclass\r\n\r\n\r\n\n\n### Describe alternatives you've considered\n\nNot really sure what alternative there is to a simple page class/id at the top (under/next to .dark?)\n\n### Additional context\n\nI have a page about forks of the application, and each fork has their own theme color\r\nRight now I try to use import css on the markdown page, but that stays on page change, and on build it gets scrambled together\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.",[2938],{"name":2939,"color":2940},"has-workaround","1B4515",2654,"Frontmatter PageClass","2023-08-06T00:04:28Z","https://github.com/vuejs/vitepress/issues/2654",0.7592474,{"description":2947,"labels":2948,"number":2949,"owner":2872,"repository":2873,"state":2930,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Is your feature request related to a problem? Please describe.\n\nyes, sometimes code samples are too large to fit on the full screen or the size of screen the user is on\n\n### Describe the solution you'd like\n\nI'd like to allow for a button next to the copy button on code blocks that allows the user to wrap the code blocks\r\n\r\n\u003Cimg width=\"190\" alt=\"testing 2023-08-18 at 10 28 07\" src=\"https://github.com/vuejs/vitepress/assets/46639943/7e404a6c-3405-4b4c-a56a-0174c49c339f\">\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.",[],2815,"Allow wrapping of code blocks","2023-08-26T00:04:05Z","https://github.com/vuejs/vitepress/issues/2815",0.76646996,{"description":2955,"labels":2956,"number":2958,"owner":2872,"repository":2873,"state":2930,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Describe the bug\r\n\r\nAttempting to run `vitepress build docs` when there exists a file `docs/**/arguments.md` results in a crash.\r\n```shell\r\n$ yarn vitepress build docs\r\nyarn run v1.22.19\r\n$ /home/.../website/node_modules/.bin/vitepress build docs\r\nvitepress v1.0.0-alpha.4\r\n⠇ building client + server bundles...[vite:esbuild-transpile] Transform failed with 1 error:\r\narguments.md.js:21:4: ERROR: Declarations with the name \"arguments\" cannot be used in strict mode\r\n\r\nDeclarations with the name \"arguments\" cannot be used in strict mode\r\n19 | return _sfc_setup ? _sfc_setup(props, ctx) : undefined\r\n20 | };\r\n21 | var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\r\n | ^\r\n22 | \r\n23 | exports.__pageData = __pageData;\r\n\r\n✖ building client + server bundles...\r\n[vite:esbuild-transpile] Transform failed with 1 error:\r\nassets/arguments.md.88297d47.js:14:4: ERROR: Declarations with the name \"arguments\" cannot be used in an ECMAScript module\r\n\r\nDeclarations with the name \"arguments\" cannot be used in an ECMAScript module\r\n12 | return (openBlock(), createElementBlock(\"div\", null, _hoisted_2))\r\n13 | }\r\n14 | var arguments = /*#__PURE__*/_export_sfc(_sfc_main, [['render',_sfc_render]]);\r\n | ^\r\n15 | \r\n16 | export { __pageData, arguments as default };\r\n\r\nbuild error:\r\n Error: Transform failed with 1 error:\r\narguments.md.js:21:4: ERROR: Declarations with the name \"arguments\" cannot be used in strict mode\r\n at failureErrorWithLog (/home/.../website/node_modules/esbuild/lib/main.js:1615:15)\r\n at /home/.../website/node_modules/esbuild/lib/main.js:1404:29\r\n at /home/.../website/node_modules/esbuild/lib/main.js:669:9\r\n at handleIncomingPacket (/home/.../website/node_modules/esbuild/lib/main.js:766:9)\r\n at Socket.readFromStdout (/home/.../website/node_modules/esbuild/lib/main.js:635:7)\r\n at Socket.emit (node:events:527:28)\r\n at addChunk (node:internal/streams/readable:315:12)\r\n at readableAddChunk (node:internal/streams/readable:289:9)\r\n at Socket.Readable.push (node:internal/streams/readable:228:10)\r\n at Pipe.onStreamRead (node:internal/stream_base_commons:190:23) {\r\n errors: [\r\n {\r\n detail: undefined,\r\n id: '',\r\n location: [Object],\r\n notes: [Array],\r\n pluginName: '',\r\n text: 'Declarations with the name \"arguments\" cannot be used in strict mode'\r\n }\r\n ],\r\n warnings: [],\r\n frame: '\\n' +\r\n '\\x1B[33mDeclarations with the name \"arguments\" cannot be used in strict mode\\x1B[39m\\n' +\r\n '19 | return _sfc_setup ? _sfc_setup(props, ctx) : undefined\\n' +\r\n '20 | };\\n' +\r\n \"21 | var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\\n\" +\r\n ' | ^\\n' +\r\n '22 | \\n' +\r\n '23 | exports.__pageData = __pageData;\\n',\r\n loc: {\r\n column: 4,\r\n file: 'arguments.md.js',\r\n length: 9,\r\n line: 21,\r\n lineText: \"var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\",\r\n namespace: '',\r\n suggestion: ''\r\n },\r\n code: 'PLUGIN_ERROR',\r\n plugin: 'vite:esbuild-transpile',\r\n hook: 'renderChunk'\r\n}\r\n```\r\n\r\n### Reproduction\r\n\r\nTo reproduce, create a file called `arguments.md` with any content inside the vitepress `docs` folder (or other target).\r\nThen, run `vitepress build \u003Cfolder>`, and the error will occur.\r\n\r\n### Expected behavior\r\n\r\nThe expected behaviour is to generate an `arguments.html` file.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.18 Arch Linux\r\n CPU: (12) x64 AMD Ryzen 5 2600X Six-Core Processor\r\n Memory: 18.11 GB / 31.28 GB\r\n Container: Yes\r\n Shell: 5.9 - /usr/bin/zsh\r\n Binaries:\r\n Node: 16.16.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 8.14.0 - /usr/bin/npm\r\n Browsers:\r\n Chromium: 103.0.5060.134\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.4 => 1.0.0-alpha.4 \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] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\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.",[2957],{"name":2904,"color":2905},1068,"Documents named `arguments.md` cannot be built.","2023-01-21T14:27:03Z","https://github.com/vuejs/vitepress/issues/1068",0.77998143,{"description":2964,"labels":2965,"number":2967,"owner":2872,"repository":2873,"state":2930,"title":2968,"updated_at":2969,"url":2970,"score":2971},"URL: https://vitepress.vuejs.org/guide/theme-home-page\r\n\r\n- General recommendation about image\r\n - Dimensions/Resolutions/Aspect Ratio\r\n - Mention the home-hero-image slot\r\n - Can be used to add videos and animated stuff \r\n- How to get the glow effect? (section similar to \"Customizing the name color\" present on that page)\r\n - Mention the CSS vars\r\n - Recommendation on how to generate gradients\r\n - If someone can spin up an online app to recommend certain gradient combinations based on user-provided image, we can add a link to that too. Or if the app is not much heavy, we can embed it itself in docs.\r\n\r\nx-ref: #1569, /cc @btea\r\n\r\nalso #1272",[2966],{"name":2866,"color":2867},1773,"Add docs about hero image","2023-08-12T00:04:21Z","https://github.com/vuejs/vitepress/issues/1773",0.7839225,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUtHj-3ZWUizLxZrZg6bYstl87PIJUGn7aJuOZ3R5HrM":-1},"/vuejs/vitepress/2406"]