\u003C/svg>',\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nAdd `width=\"24\" height=\"24\" `attribute\r\nLike this\r\n```txt\r\n'\u003Csvg xmlns=\"http://www.w3.org/2000/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\">' \r\n```\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 6.3 Kali GNU/Linux Rolling 2023.3\r\n CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz\r\n Memory: 8.21 GB / 15.24 GB\r\n Container: Yes\r\n Shell: 5.9 - /usr/bin/zsh\r\n Binaries:\r\n Node: 18.13.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.2.0 - /usr/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.179\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.10 => 1.0.0-rc.10\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.",[2890,2893,2896],{"name":2891,"color":2892},"theme","0754FB",{"name":2894,"color":2895},"a11y","fbca04",{"name":2869,"color":2870},2930,"themeConfig.socialLinks.icon ","2024-02-02T09:23:16Z","https://github.com/vuejs/vitepress/issues/2930",0.800202,{"description":2903,"labels":2904,"number":2909,"owner":2872,"repository":2873,"state":2874,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Describe the bug\r\n\r\nThe theme docs and code completion state that the `router` instance is exposed in `enhanceApp()` but it appears the `router` instance is actually a `route` instance, and doesn't conform to the [Router](https://vitepress.dev/reference/runtime-api#userouter) interface.\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nInitialize a new project, then add the following code to `enhanceApp()`:\r\n\r\n```ts\r\n console.log({ router })\r\n router.onAfterRouteChanged((to: string) => {\r\n console.log(`changed to: ${to}`)\r\n })\r\n```\r\n\r\n### Expected behavior\r\n\r\nWe should be able to interact with the `router` instance\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.5\r\n CPU: (12) arm64 Apple M3 Pro\r\n Memory: 213.02 MB / 36.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.15.1 - /usr/local/bin/node\r\n Yarn: 1.22.22 - /usr/local/bin/yarn\r\n npm: 10.7.0 - /usr/local/bin/npm\r\n pnpm: 8.15.6 - /usr/local/bin/pnpm\r\n Browsers:\r\n Brave Browser: 122.1.63.169\r\n Chrome: 128.0.6613.138\r\n Chrome Canary: 130.0.6720.0\r\n Edge: 128.0.2739.79\r\n Safari: 17.5\r\n npmPackages:\r\n vitepress: ^1.3.4 => 1.3.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] 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.",[2905,2908],{"name":2906,"color":2907},"docs","0075ca",{"name":2869,"color":2870},4204,"`enhanceApp()` `ctx.router` is not a router instance","2024-10-26T17:17:21Z","https://github.com/vuejs/vitepress/issues/4204",0.804009,{"description":2915,"labels":2916,"number":2918,"owner":2872,"repository":2873,"state":2874,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Is your feature request related to a problem? Please describe.\r\n\r\nright now the appearance has the following type:\r\n\r\n```\r\nappearance?: boolean | 'dark' | 'force-dark' | 'force-auto' | (Omit\u003CUseDarkOptions, 'initialValue'> & {\r\n initialValue?: 'dark';\r\n });\r\n```\r\nthe `Omit\u003CUseDarkOptions, 'initialValue'>` allows to have only valueDark and valueLight, but it does not allow me to have other modes different than dark/light such as custom mode created by the developer giving further color customisation to the theme: light|dark|luxury|business and so on.\r\n\r\n### Describe the solution you'd like\r\n\r\ni would like to have the possibility to use multiple modes in addition to dark/light. so that the appearance type becomes something like:\r\n\r\n```\r\ninterface Appearance\u003CT extends string> {\r\n appearance?: boolean | 'dark' | 'force-dark' | 'force-auto' | (Omit\u003CUseColorModeOptions\u003CT>, 'initialValue'> & {\r\n initialValue?: 'dark';\r\n });\r\n}\r\n```\r\n\r\nwhere T is a union type of color modes like 'light'|'dark'|'luxury'|'business' that the developer will specify\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 this is not possible please provide a solution in the case where:\r\n1) I override the theme switcher with a custom theme switcher created by me containing different modes\r\n2) I still have to keep the appearance to be not false in the config.ts else the switcher will disappear\r\n\r\nmy current workaround is to use the `vitepress-theme-appearance` as `storageKey` in my custom component\r\n```\r\n type AvailableTheme = 'light' | 'dark' | 'gourmet';\r\n\r\nconst theme = useColorMode\u003CAvailableTheme>({\r\n attribute: 'data-theme',\r\n storageKey: 'vitepress-theme-appearance',\r\n modes: {\r\n // custom colors\r\n light: 'light',\r\n dark: 'dark',\r\n gourmet: 'gourmet',\r\n },\r\n initialValue: 'dark',\r\n});\r\n```\r\n\r\nthat would be fine if the component would not be a part of a vue components package i am building. yeah, i could still pass the storageKey as props and let the developer handle it if needed, but it might not be the best option.\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.",[2917],{"name":2869,"color":2870},4471,"allow multiple different color modes in addition to light|dark for themes","2025-03-02T18:07:55Z","https://github.com/vuejs/vitepress/issues/4471",0.80411845,{"description":2924,"labels":2925,"number":2930,"owner":2872,"repository":2873,"state":2874,"title":2931,"updated_at":2932,"url":2933,"score":2934},"**Describe the bug**\r\nI built and published vitepress pages to my Azure App Service by ASP.Net Core project, but got Hydration completed but contains mismatches error when i review, and the index page and other pages rendered not correctlly. But it runs perfectly on my local within dev mode\r\n\r\n\r\n\r\nCorrecting render:\r\n\r\n\r\n\r\n\r\n**Expected behavior**\r\nAll page displays correctlly.\r\n\r\n**index.md**\r\n```\r\n---\r\nlayout: home\r\ntitle: SD-LINES デベロッパーポータル\r\n\r\nhero:\r\n name: \"SD-LINES ドキュメンテーション\"\r\n tagline: 当社のサービスでウェブサイトの可能性を高めましょう\r\n actions:\r\n - theme: brand\r\n text: 詳しくはこちら\r\n link: /ja/docs/overview/about\r\n\r\nfeatures:\r\n - title: ユニークで魅力的な広告\r\n details: 専門的に最適化された広告表示で、訪問者を魅了し、関与させることでウェブサイトの魅力を高めます\r\n - title: 効果の即時洞察\r\n details: 詳細な分析により広告のパフォーマンスを即座に把握し、戦略を効果的に調整し、改善することができます\r\n - title: 迅速かつ正確な検索\r\n details: ユーザーが製品を迅速かつ簡単に見つけることができるように支援し、これまでにないシームレスなオンラインショッピング体験を提供します。\r\n\r\n---\r\n\r\n```\r\n\r\n**config.mts**\r\n```typescript\r\nimport { defineConfig } from 'vitepress'\r\nimport { sidebar } from './config/sidebar'\r\n\r\nexport default defineConfig({\r\n title: \"SD-LINES Developer\",\r\n description: \"SD-LINES Developer Documentation\",\r\n head: [\r\n ['link', { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }]\r\n ],\r\n themeConfig: {\r\n logo: '/logo.svg',\r\n \r\n sidebar,\r\n lastUpdated: {\r\n text: 'Last updated',\r\n formatOptions: {\r\n dateStyle: 'medium',\r\n timeStyle: 'short'\r\n }\r\n },\r\n search: {\r\n provider: 'local'\r\n },\r\n },\r\n markdown: {\r\n lineNumbers: true\r\n },\r\n cleanUrls: true,\r\n lastUpdated: true,\r\n locales: {\r\n root: {\r\n label: '日本語',\r\n lang: 'ja',\r\n link: '/ja/',\r\n themeConfig: { \r\n nav: [\r\n { text: 'Home', link: '/ja/' },\r\n { text: 'Guides', link: '/ja/docs/overview/about' },\r\n { text: 'Reference', link: '/ja/reference/market' }\r\n ],\r\n }\r\n },\r\n en: {\r\n label: 'English',\r\n lang: 'en',\r\n link: '/en/',\r\n themeConfig: { \r\n nav: [\r\n { text: 'Home', link: '/en/' },\r\n { text: 'Guides', link: '/en/docs/overview/about' },\r\n { text: 'Reference', link: '/en/reference/market' }\r\n ],\r\n }\r\n },\r\n }\r\n})\r\n```\r\n\r\n**What I tried**\r\nMy site is not using Cloudflare's.",[2926,2929],{"name":2927,"color":2928},"need more info","bdbefc",{"name":2869,"color":2870},3780,"hydration mismatch with default build","2024-10-12T12:12:20Z","https://github.com/vuejs/vitepress/issues/3780",0.808504,{"description":2936,"labels":2937,"number":2938,"owner":2872,"repository":2873,"state":2939,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Describe the bug\n\nSetting 'auto' to a sidebar property in config.js does not create automatic sidebar elements.\n\n### Reproduction\n\n```\r\n sidebar: {\r\n '/projects/': 'auto',\r\n }\r\n```\n\n### Expected behavior\n\n A sidebar should be auto generated using the headings provided in the markdown files for the projects page\n\n### System Info\n\n```Text\nvitepress version: 1.0.2\r\nvite version: 1.0.0\r\nNode version: v21.6.1\r\nOS version: Windows 11 Pro 23H2\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.",[],3755,"closed","Automatic Headings in Sidebar","2024-04-28T12:24:54Z","https://github.com/vuejs/vitepress/issues/3755",0.7374175,{"description":2945,"labels":2946,"number":2949,"owner":2872,"repository":2873,"state":2939,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Describe the bug\n\nIf deploy from local Mac - all is ok\r\nBut if deploy(from docker CI GitLab) - error in rollup package\r\n\r\n\n\n### Reproduction\n\n`npm run docs:build`\n\n### Expected behavior\n\nNo error is needed\n\n### System Info\n\n```Text\nRunning with gitlab-runner 16.11.0~pre.21.gaa21be2d (aa21be2d)\r\n on blue-4.saas-linux-small-amd64.runners-manager.gitlab.com/default\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.",[2947,2948],{"name":2866,"color":2867},{"name":2869,"color":2870},3812,"Deploy error","2024-07-16T04:42:14Z","https://github.com/vuejs/vitepress/issues/3812",0.77032304,{"description":2955,"labels":2956,"number":2958,"owner":2872,"repository":2873,"state":2939,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Is your feature request related to a problem? Please describe.\n\nI want to use the existing structure of VitePress, with kind of the same Layout, but different styling. I was thinking I would just build a custom theme, but it seems like I cannot access e.g. the navbar configs. Or at least I wouldnt know how?\n\n### Describe the solution you'd like\n\nI would like to know how I can build my own custom theme, using all the default data that i would provide otherwise using the default theme.\n\n### Describe alternatives you've considered\n\nUsing the default theme but changing it up, but I doubt that it's flexible enough. another thing would be to just for vitepress and implementing my own default theme, but I doubt that it's thought to be done like that.\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.",[2957],{"name":2891,"color":2892},912,"Extending/Mimicing default components in custom theme","2023-01-21T14:32:40Z","https://github.com/vuejs/vitepress/issues/912",0.77915883,{"description":2964,"labels":2965,"number":2966,"owner":2872,"repository":2873,"state":2939,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Describe the bug\n\nvitepress dev is normal, but vitepress build reports an error, SyntaxError: Element is missing end tag. The key is that it is impossible to locate where the end tag is missing.\n\n### Reproduction\n\nvitepress build\n\n### Expected behavior\n\nPack normally or provide specific error information\n\n### System Info\n\n```Text\n\"vitepress\": \"^1.1.4\"\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.",[],3876,"SyntaxError: Element is missing end tag.","2024-05-31T04:42:05Z","https://github.com/vuejs/vitepress/issues/3876",0.78347754,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fz93DYYP6-kB4-AykFa0bW6t3gK_Q3Xv2t8fGelVOVFk":-1},"/vuejs/vitepress/3965"]