\r\n title: Feature A\r\n details: Lorem ipsum dolor sit amet, consectetur adipiscing elit\r\n```\r\n\r\nCheck the feature icon type\r\n```ts\r\ntype FeatureIcon =\r\n | string\r\n | { src: string; alt?: string; width?: string; height: string }\r\n | {\r\n light: string\r\n dark: string\r\n alt?: string\r\n width?: string\r\n height: string\r\n }\r\n```\r\n\r\nI refer to the render logic, use `v-html` render the icon.\r\nDisplay well in `dev` environment, but shows errors in `prod` environment.\r\n\r\n| dev | build |\r\n| ----------- | ----------- |\r\n|  |  |\r\n\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/github/zyyv/vitepress-unocss-issue\r\n\r\n- Display right run `pnpm dev`\r\n- Display error run `pnpm build && pnpm preview`\r\n\r\n### Expected behavior\r\n\r\nDev and build behave the same\r\n\r\n### System Info\r\n\r\n```Text\r\nlatest\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.",[3020,3023,3026],{"name":3021,"color":3022},"build","377ba8",{"name":3024,"color":3025},"has-workaround","1B4515",{"name":3027,"color":3028},"stale","ededed",4045,"vuejs","vitepress","open","SSR in dev for more consistent output in dev and prod","2025-03-02T18:08:58Z","https://github.com/vuejs/vitepress/issues/4045",0.71834546,{"description":3038,"labels":3039,"number":3047,"owner":3030,"repository":3031,"state":3032,"title":3048,"updated_at":3049,"url":3050,"score":3051},"### Describe the bug\n\nI have few *.md pages where I use custom globally registered Vue component to display formatted output. Display of such page using URL is as expected. But when I create `createContentLoader` and enable `render: true` option then I get HTML code without rendered Vue component, as a custom tag.\n\n### Reproduction\n\nI prepared stackblitz code reproducing this issue. Link single card works as expected. card list loads data dynamically and displays the received html content.\r\n\r\nhttps://stackblitz.com/edit/vite-8wtjts\n\n### Expected behavior\n\nThe `render: true` in `createContentLoader` should return also rendered Vue component instead of inline tag.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 11.7.10\r\n CPU: (4) x64 Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz\r\n Memory: 87.34 MB / 8.00 GB\r\n Shell: 3.2.57 - /bin/bash\r\n Binaries:\r\n Node: 18.13.0 - /usr/local/bin/node\r\n npm: 9.8.1 - /usr/local/bin/npm\r\n pnpm: 8.9.1 - /usr/local/bin/pnpm\r\n Browsers:\r\n Chrome: 118.0.5993.117\r\n Safari: 16.6.1\r\n npmPackages:\r\n vitepress: 1.0.0-rc.24 => 1.0.0-rc.24\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,3046],{"name":3041,"color":3042},"docs","0075ca",{"name":3044,"color":3045},"wont fix","EDEED1",{"name":3027,"color":3028},3147,"createContentLoader do not render Vue components in html output","2025-03-02T18:10:27Z","https://github.com/vuejs/vitepress/issues/3147",0.725642,{"description":3053,"labels":3054,"number":3058,"owner":3030,"repository":3031,"state":3032,"title":3059,"updated_at":3060,"url":3061,"score":3062},"",[3055],{"name":3056,"color":3057},"need more info","bdbefc",4604,"是否会支持webdav备份?","2025-03-07T09:28:52Z","https://github.com/vuejs/vitepress/issues/4604",0.7412254,{"description":3064,"labels":3065,"number":3068,"owner":3030,"repository":3031,"state":3032,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### Describe the bug\n\nas we create too deep folders , appear the fault : file name too long while build\n\n### Reproduction\n\ncreate too deep folders\n\n### Expected behavior\n\nexcept can build success, even zhe folders is deep and each folder name is long\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.16299\r\n CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz\r\n Memory: 5.00 GB / 15.89 GB\r\n Binaries:\r\n Node: 20.9.0 - D:\\program\\nvm1.1.11\\nodejs\\node.EXE\r\n npm: 10.1.0 - D:\\program\\nvm1.1.11\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (41.16299.1480.0)\r\n Internet Explorer: 11.0.16299.371\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.44 => 1.0.1\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.",[3066,3067],{"name":3021,"color":3022},{"name":3027,"color":3028},3763,"file name too long ","2025-03-02T18:09:25Z","https://github.com/vuejs/vitepress/issues/3763",0.7439854,{"description":3074,"labels":3075,"number":3078,"owner":3030,"repository":3031,"state":3032,"title":3079,"updated_at":3080,"url":3081,"score":3082},"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_",[3076,3077],{"name":3021,"color":3022},{"name":3027,"color":3028},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.74710566,{"description":3084,"labels":3085,"number":3089,"owner":3030,"repository":3031,"state":3032,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Is your feature request related to a problem? Please describe.\r\n\r\nWhen building with **Vite** and using multiple .env.* files, there is a [mode](https://vitejs.dev/guide/env-and-mode.html#modes) flag which essentially tells Vite to load the `.env.\u003Cmode>` file. By default, this flag is set to `production` when running the `build` command.\r\n\r\nLet's say I have 3 .env.* files:\r\n- .env - my default localhost dev env file\r\n- .env.uat - the env file I wish to use when deploying to UAT\r\n- .env.prod - the env file I wish to use when deploying to PROD\r\n\r\nHaving a Vite app, in dev mode (`vite dev`) the default .env file is loaded, and when running build I can pass the mode I wish (e.g. `vite build --mode uat`), usually coming as an arg from my build config.\r\n\r\n**_What happens when using VitePress?_**\r\n\r\nVitePress takes only the default Vite behaviour, which is to set the mode to `production` when running `vitepress build`. Passing the `--mode` flag has no effect. The development server (`vitepress dev`) loads the default .env file correctly (`.env`).\r\n\r\n### Describe the solution you'd like\r\n\r\nVitePress should honour the `--mode` flag in the same manner as Vite does.\r\n\r\n### Describe alternatives you've considered\r\n\r\nMy current workaround is to manually rename different .env.* files to `.env.production` before `vitepress build`, even if I am not building for a production environment. This works, but is not ideal, and certainly not consistent with my other Vite/Vue apps.\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.",[3086,3087,3088],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},2692,"VitePress should mimic Vite's --mode flag when running \"vitepress build\"","2025-03-02T18:11:11Z","https://github.com/vuejs/vitepress/issues/2692",0.7532849,{"description":3095,"labels":3096,"number":3098,"owner":3030,"repository":3031,"state":3032,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Is your feature request related to a problem? Please describe.\n\nI would like to use vitepress for my blog, which contains a lot of images. \r\nCurrently I use a lightbox library to visualise the images.\r\nThe following changes I made to integerate a lightbox library. It works, but I'm not 100% happy with it.\n\n### Describe the solution you'd like\n\nFirst, I installed a new markdown-it plugin.\r\n\r\n`npm i -D markdown-it-div`\r\n\r\nConfigured it to suit my needs\r\n\r\n```\r\n\u003C!-- .vitepress\\config.mts -->\r\n\r\nimport markdownItDiv from 'markdown-it-div'\r\n\r\nexport default defineConfig({\r\n markdown: {\r\n config: (md) => {\r\n md.use(markdownItDiv, { marker: '=' });\r\n }\r\n }\r\n})\r\n```\r\n\r\nThen I added a theme `index.css` and added my custom css to it to display a collection of images in a nice way.\r\n\r\n```\r\n\u003C!-- .vitepress\\theme\\index.css -->\r\n\r\ndiv.gallery p {\r\n display: flex;\r\n flex-wrap: wrap;\r\n align-items: flex-start;\r\n flex-direction: row;\r\n \r\n}\r\n\r\ndiv.gallery p a img {\r\n margin: 10px;\r\n border: 0px solid #000;\r\n box-shadow: 3px 3px 8px 0px rgba(0,0,0,0.3); \r\n max-width: 23vw;\r\n}\r\n```\r\n\r\nI chose the plain javascript fslightbox library. I downloaded the [fslightbox.js](https://fslightbox.com/javascript/download) and put it in `public\\libs\\fslightbox.js`\r\n\r\nThen I registered this *.js file at the top of each page by modifying the config.mdx file.\r\n\r\n```\r\n\u003C!-- .vitepress\\config.mts -->\r\n\r\nexport default defineConfig({\r\n head: [\r\n [\r\n 'script',\r\n { src: '/libs/fslightbox.js' }\r\n ] \r\n ],\r\n})\r\n```\r\n\r\nIn order for the fslightbox library to load images as lightboxes, I need to call `refreshFsLightbox();` after a page is loaded or changed. I did this by modifying the theme `index.ts` file.\r\n\r\n```\r\n\u003C!-- .vitepress\\theme\\index.ts -->\r\n\r\nimport DefaultTheme from 'vitepress/theme';\r\nimport { onMounted, watch, nextTick } from 'vue';\r\nimport { useRoute } from 'vitepress';\r\n\r\nimport './index.css';\r\n\r\nexport default {\r\n ...DefaultTheme, \r\n setup() {\r\n const route = useRoute();\r\n const initLightbox = () => {\r\n console.log('Log from Theme onMounted before fsLightboxInstances', window.fsLightboxInstances)\r\n refreshFsLightbox();\r\n console.log('Log from Theme onMounted after fsLightboxInstances', window.fsLightboxInstances)\r\n };\r\n onMounted(() => {\r\n initLightbox();\r\n });\r\n watch(\r\n () => route.path,\r\n () => nextTick(() => initLightbox())\r\n );\r\n },\r\n};\r\n```\r\n\r\nNow I'm ready to use it. To do this, I need to put my full-size pictures in the \\public\\ folder and my thumbnails in the post folder.\r\n\r\n```\r\n.\r\n└── simple-blog/\r\n ├── .vitepress\r\n ├── blog/\r\n │ └── post-01/\r\n │ ├── img_1-thumb.jpg\r\n │ ├── img_2-thumb.jpg\r\n │ ├── img_3-thumb.jpg\r\n │ └── index.md\r\n └── public/\r\n └── post-01/\r\n ├── img_1.jpg\r\n ├── img_2.jpg\r\n └── img_3.jpg\r\n```\r\n\r\nI can now write something like this in a post:\r\n\r\n```\r\n# My First Post\r\n\r\n=== .gallery\r\n[](/blog/post-01/IMG_1.jpg){data-fslightbox=\"gallery\"}\r\n[](/blog/post-01/IMG_2.jpg){data-fslightbox=\"gallery\"}\r\n[](/blog/post-01/IMG_3.jpg){data-fslightbox=\"gallery\"}\r\n[](/blog/post-01/IMG-4.jpg){data-fslightbox=\"gallery\"}\r\n===\r\n```\r\n\r\n\r\nThe part \r\n\r\n`=== .gallery`\r\n\r\n is converted by the markdown-it plugin \"markdown-it-div\" to html like \r\n\r\n`\u003Cdiv class=\"gallery\">\u003C/div>`\r\n\r\nand styled nicely by my adjustments to the css.\r\n\r\nA link with an image is described by \r\n\r\n`[](/blog/post-01/IMG_1.jpg){data-fslightbox=\"gallery\"}`\r\n\r\n and would be converted to \r\n\r\n`\u003Ca href=\"/blog/post-01/IMG_1.jpg\" data-fslightbox=\"gallery\">\u003Cimg src=\"/blog/post-01/IMG_1-thumb.jpg\" alt=\"\">\u003C/a>`\r\n\r\nhtml out of the box.\n\n### Describe alternatives you've considered\n\nAs I mentioned previously it works as expected but I'm not happy with it.\r\n- Are there any plans to integrate a feature like lightbox directly into vitepress?\r\n- I would like to have all post-released files in a separate folder.\r\n\t- With my solution I have to put the full images in the \\public\\ folder. \r\n\t\t- This is because they are linked with an a-tag and are not automatically copied to the dist folder.\r\n\t\t- The thumbnail images I can have in the post-release folder because they are reverenced as images with an img-tag and therefore its automatically copied to the dist folder.\r\n\t- In this day and age of fast internet is it even necessary to separate thumbnails and full size images?\r\n\t- Is there a better solution that I'm not getting?\r\n\r\nIt would be really nice if I could just reference the full image and have the thumbnail generated automatically during build. \r\nThen I would just have to write \r\n\r\n```\r\nimg-group(IMG_1.jpg)\r\nimg-group(IMG_2.jpg)\r\nimg-group(IMG_3.jpg)\r\nimg-group(IMG_4.jpg)\r\n``` \r\n\r\nand it would automatically be wrapped in a nicely styled div with image links that would be opened by a lightbox library and display automatically generated thumbnails.\r\n\r\n\r\nOr is there even a way to wrap this functionally into a plugin? I have not found any information on how to write a plugin.\r\n- The plugin system would need some hook for the build to create thumbnail images.\r\n- Also there are some special markdown rules that need to be added to the plugin.\r\n- Also some custom css and javascript is necessary to add via plugin.\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.",[3097],{"name":3027,"color":3028},3855,"Support for lightbox image galleries","2024-12-03T17:28:18Z","https://github.com/vuejs/vitepress/issues/3855",0.75529236,{"description":3104,"labels":3105,"number":3109,"owner":3030,"repository":3031,"state":3110,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Describe the bug\n\nthis is my `config.mts`\n```\nimport type { DefaultTheme } from 'vitepress';\nimport { defineConfig } from 'vitepress';\n\nexport default defineConfig({\n base: '/flyonui-vue/',\n rewrites(id) {\n // PascalCase to kebab-case for route urls\n return id.replace(/([a-z0–9])([A-Z])/g, '$1-$2').toLowerCase();\n },\n title: 'FlyonUI Vue',\n cleanUrls: true,\n head: [\n ['link', { rel: 'icon', type: 'image/svg', href: '/assets/logo.svg' }],\n ],\n themeConfig: {\n sidebar: getSidebar(),\n logo: '/assets/logo.svg',\n search: {\n provider: 'local',\n },\n socialLinks: [\n { icon: 'github', link: 'https://github.com/michaelcozzolino/flyonui-vue' },\n ],\n\n footer: {\n message: 'Released under the MIT License.',\n copyright: '© 2025 FlyonUI Vue', // todo: add automatic date change\n },\n },\n});\n\nfunction getSidebar(): DefaultTheme.SidebarItem[] {\n return [\n {\n text: 'Getting Started',\n items: [\n {\n items: [\n {\n text: 'Quick Start',\n link: 'quick-start',\n },\n ],\n },\n ],\n },\n {\n text: 'Vue Components',\n items: [\n {\n text: 'Components',\n base: '/components/',\n items: [\n // { text: 'Accordion', link: 'accordion' },\n // { text: 'Alert', link: 'alert' },\n // { text: 'Avatar', link: 'avatar' },\n { text: 'Badge', link: 'badge' },\n { text: 'Button', link: 'button' },\n // { text: 'Card', link: 'card' },\n // { text: 'Carousel', link: 'carousel' },\n // { text: 'Chat Bubble', link: 'chat-bubble' },\n // { text: 'Collapse', link: 'collapse' },\n // { text: 'Diff', link: 'diff' },\n // { text: 'Indicator', link: 'indicator' },\n { text: 'List Group', link: 'list-group' },\n { text: 'Loading', link: 'loading' },\n // { text: 'Progress', link: 'progress' },\n // { text: 'Radial Progress', link: 'radial-progress' },\n // { text: 'Remove Element', link: 'remove-element' },\n // { text: 'Skeleton', link: 'skeleton' },\n // { text: 'Stack', link: 'stack' },\n { text: 'Stat List', link: 'stat-list' },\n // { text: 'Swap', link: 'swap' },\n // { text: 'Theme Controller', link: 'theme-controller' },\n // { text: 'Timeline', link: 'timeline' },\n // { text: 'Tree View', link: 'tree-view' },\n ],\n },\n {\n text: 'Navigations',\n base: '/navigations/',\n items: [\n { text: 'Menu', link: 'menu' },\n { text: 'Navbar', link: 'navbar' },\n ],\n },\n {\n text: 'Forms',\n base: '/forms/',\n items: [\n { text: 'Select', link: 'select' },\n { text: 'Checkbox', link: 'checkbox' },\n ],\n },\n ],\n },\n {\n items: [\n {\n text: 'Extra',\n base: '/extra/',\n items: [\n {\n text: 'Build Size Visualizer',\n link: 'build-size-visualizer',\n },\n ],\n },\n ],\n },\n ];\n}\n\n```\nWhen i go to the quick-start page the next page at the bottom is still quick-start. when I go to other pages it doesn't happen.\n\n### Reproduction\n\nto see it go to: https://michaelcozzolino.github.io/flyonui-vue/quick-start\n\nto reproduce in local:\n1. git clone https://github.com/michaelcozzolino/flyonui-vue.git\n2. in the root `yarn install && yarn dev`\n3. go to the given localhost url\n\n### Expected behavior\n\nIt should show the next page that is the badge one\n\n\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\n Memory: 20.27 GB / 30.23 GB\n Container: Yes\n Shell: 5.2.21 - /bin/bash\n Binaries:\n Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node\n Yarn: 4.6.0 - ~/.yarn/bin/yarn\n npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm\n Browsers:\n Brave Browser: 132.1.74.51\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":3107,"color":3108},"bug: pending triage","e99695",4553,"closed","Next page is not correctly chosen","2025-02-17T04:43:23Z","https://github.com/vuejs/vitepress/issues/4553",0.73825127,{"description":3116,"labels":3117,"number":3119,"owner":3030,"repository":3031,"state":3110,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Describe the bug\n\nimport `svg` with plugin vite-svg-loader\r\nit's type should be `FunctionalComponent`\r\nthis is ok in vite projects\r\nbut not work in vitepress\r\nit's type is `String`\n\n### Reproduction\n\nhttps://github.com/x-wink/wink-ui\r\nthis is my repository\r\nthrow type error in this file: `docs\\src\\examples\\button\\use5.vue`\r\nit's ok in this file: `packages\\components\\select\\tag.vue`\n\n### Expected behavior\n\njust like vite projects\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (24) x64 Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz\r\n Memory: 19.04 GB / 31.86 GB\r\n Binaries:\r\n Node: 18.16.0 - D:\\nodejs\\node.EXE\r\n npm: 9.5.1 - D:\\nodejs\\npm.CMD\r\n pnpm: 8.7.4 - ~\\AppData\\Local\\pnpm\\pnpm.CMD\r\n Browsers:\r\n Chrome: bookmarks.html\r\ninitial_preferences\r\n Edge: Chromium (116.0.1938.81)\r\n Internet Explorer: 11.0.19041.1566\n```\n\n\n### Additional context\n\nexists follow projects in my UI libary momorepo:\r\n- docs\r\n- icons\r\n- components\r\n- wink-ui\r\n\r\n`docs` is a vitepress project, dependencie `icons` and `components`\r\n`icons` is a vite project with plugin vite-svg-loader\r\n`components` define vue components and dependencie `icons`\r\n`wink-ui` is a vite project dependencie `components`, build and emits `components`\r\n\r\nI try to upgrade vitepress to latest version,it's same result.\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.",[3118],{"name":3056,"color":3057},2968,"Type error when use svg icon with plugin vite-svg-loader","2024-01-09T00:05:11Z","https://github.com/vuejs/vitepress/issues/2968",0.738763,{"description":3125,"labels":3126,"number":3128,"owner":3030,"repository":3031,"state":3110,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Describe the bug\r\n\r\n>If the css logo of my css code block is uppercase (CSS) like the following\r\n\r\n>\\```CSS\r\n>p{}\r\n>\\```\r\n\r\n* When building it produces an error like this:`[vitepress] No language registration for CSS`\r\n\r\n### Reproduction\r\n\r\n`pnpm build`-->cause an error,\r\n`pnpm dev`-->and the preview also creates problems\r\n\r\n### Expected behavior\r\n\r\nCase insensitive on code block identifiers\r\n\r\n### System Info\r\n\r\n```shell\r\n[vite] Internal server error: No language registration for CSS\r\n Plugin: vitepress\r\n File: E:/Project/CSS/blog-css/docs/css布局/grid.md\r\n at getGrammar (E:\\Project\\CSS\\blog-css\\node_modules\\.pnpm\\shiki@0.10.1\\node_modules\\shiki\\dist\\index.js:2175:19)\r\n at codeToThemedTokens (E:\\Project\\CSS\\blog-css\\node_modules\\.pnpm\\shiki@0.10.1\\node_modules\\shiki\\dist\\index.js:2184:30)\r\n at Object.codeToHtml (E:\\Project\\CSS\\blog-css\\node_modules\\.pnpm\\shiki@0.10.1\\node_modules\\shiki\\dist\\index.js:2201:24)\r\n at Object.highlight (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:31999:26) \r\n at default_rules.fence (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:25746:27) \r\n at md.renderer.rules.fence (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:32339:16)\r\n at md.renderer.rules.fence (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:32828:21)\r\n at Object.md.renderer.rules.fence (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:32803:12)\r\n at Renderer$1.render (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:26025:38) \r\n at MarkdownIt.render (file:///E:/Project/CSS/blog-css/node_modules/.pnpm/vitepress@1.0.0-alpha.1/node_modules/vitepress/dist/node/serve-e8d58be3.js:31950:24)\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.",[3127],{"name":3107,"color":3108},772,"No language registration for CSS","2023-01-21T14:34:15Z","https://github.com/vuejs/vitepress/issues/772",0.74056834,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fE-B0j8-CijaG7oE4_ND_z8JtjUQzllwU9IjzSSa9CF4":-1},"/vuejs/vitepress/3472"]