'\n\n html.value = await codeToHtml(code, {\n lang: 'vue',\n theme: 'material-theme-ocean',\n })\n})\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv v-html=\"html\">\u003C/div>\n\u003C/template>\n```\n5. Put this code into a `.md` file:\n```md\n---\nlayout: page\nsidebar: false\n---\n\n\u003Cscript setup>\nimport CustomComponent from './CustomComponent.vue'\n\u003C/script>\n\n\u003CCustomComponent />\n```\n5. `pnpm build && pnpm docs:build`\n6. `pnpm preview`\n - Open the page where the Shiki is used.\n - Open DevTools → Network tab.\n - Notice that only the Vue grammar and material-theme-ocean chunks are fetched. This is correct. ✅\n7. `pnpm docs:preview`\n- Open the page where the Shiki is used.\n- Open DevTools → Network tab.\n- Notice that all Shiki languages and themes (even those not in use) are fetched at page load. This is incorrect. ❌\n\n### Expected behavior\n\nWhen building VitePress production site with `pnpm docs:build`, the output should behave like a standard Vue production build (`pnpm build`) when using libraries such as Shiki: the production page should not fetch every chunk up front at page load; it should only fetch the chunks when they are needed.\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H\n Memory: 33.51 GB / 63.67 GB\n Binaries:\n Node: 22.11.0 - C:\\Program Files\\nodejs\\node.EXE\n Yarn: 1.22.22 - ~\\AppData\\Roaming\\npm\\yarn.CMD\n npm: 11.4.1 - C:\\Program Files\\nodejs\\npm.CMD\n pnpm: 10.11.0 - ~\\AppData\\Local\\pnpm\\pnpm.EXE\n Browsers:\n Edge: Chromium (130.0.2849.80)\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\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.",[2944],{"name":2866,"color":2867},4770,"VitePress build eagerly loads all Shiki chunks instead of lazy-loading only what's needed","2025-06-03T04:11:18Z","https://github.com/vuejs/vitepress/issues/4770",0.71479005,{"description":2951,"labels":2952,"number":2954,"owner":2869,"repository":2870,"state":2871,"title":2955,"updated_at":2956,"url":2957,"score":2958},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nWhen I use the components directly in markdown file, It raised a waring with `vue.js:1099 [Vue warn]: Failed to resolve componen` as:\r\n\r\n\r\n\r\nDoes vitepress auto register components in `.vitepress/components`? or where can I put the `.vue` files and how to use them? thank you.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\n**System Info**\r\n- vitepress version:\r\n- vite version:\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2953],{"name":2866,"color":2867},60,"Is vitepress auto register components in `.vitepress/components`?","2023-01-21T16:25:31Z","https://github.com/vuejs/vitepress/issues/60",0.71485615,["Reactive",2960],{},["Set"],["ShallowReactive",2963],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f403bXWn4-4cdatooO6OYETo7FibJ3gPfVLcrC7Z2nJg":-1},"/vuejs/vitepress/94"]