\u003C/template>\r\n \u003Ctemplate #nav-bar-title-after>\u003Cslot name=\"nav-bar-title-after\" />\u003C/template>\r\n \u003Ctemplate #nav-bar-content-before>\u003Cslot name=\"nav-bar-content-before\" />\u003C/template>\r\n \u003Ctemplate #nav-bar-content-after>\u003Cslot name=\"nav-bar-content-after\" />\u003C/template>\r\n \u003Ctemplate #nav-screen-content-before>\u003Cslot name=\"nav-screen-content-before\" />\u003C/template>\r\n \u003Ctemplate #nav-screen-content-after>\u003Cslot name=\"nav-screen-content-after\" />\u003C/template>\r\n\u003C/VPNav>\r\n\u003Cslot name=\"nav-bar-after\" />\r\n\u003CVPLocalNav :open=\"isSidebarOpen\" @open-menu=\"openSidebar\" />\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\n在markdown文件中加入图片元素,在js中改变图片元素到id和class为VPContent的元素之前或内部的第一个子元素\r\n```\r\n---\r\nlayout: doc\r\ntitle: xxx\r\ncover: '/xxx.jpg'\r\n---\r\n\r\n\u003Cscript setup>\r\nimport { useData } from 'vitepress'\r\nimport { onMounted, onUnmounted } from 'vue'\r\nconst data = useData()\r\nlet vContentPaddingTop = ''\r\nonMounted(() => {\r\n const img = document.getElementById('cover')\r\n const vContent = document.getElementById('VPContent')\r\n vContentPaddingTop = vContent.style.paddingTop\r\n vContent.style.paddingTop = '0px'\r\n img.firstChild.setAttribute('src', data.frontmatter.value.cover)\r\n img.firstChild.style.objectFit = 'cover'\r\n img.firstChild.style.objectPosition = '50% 60%'\r\n img.style.display = 'block'\r\n vContent.insertBefore(img, vContent.firstChild)\r\n})\r\nonUnmounted(() => {\r\n const img = document.getElementById('cover')\r\n const vContent = document.getElementById('VPContent')\r\n vContent.style.paddingTop = vContentPaddingTop\r\n img.style.display = 'none'\r\n})\r\n\u003C/script>\r\n\r\n\u003Cdiv class=\"cover\" id=\"cover\">\u003Cimg :src=\"$frontmatter.cover\" />\u003C/div>\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.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.",[2882,2883],{"name":2866,"color":2867},{"name":2869,"color":2870},2706,"默认主题增加nav-bar-after的slot","2025-03-02T18:11:10Z","https://github.com/vuejs/vitepress/issues/2706",0.8204284,{"description":2890,"labels":2891,"number":2896,"owner":2872,"repository":2873,"state":2874,"title":2897,"updated_at":2898,"url":2899,"score":2900},"### Describe the bug\n\nI cannot for the life of me get the `Next Page` button to show anything but the first page (in this case `Introduction`) I know there are several issues that have been closed about this same topic, but their resolutions are all to use absolute URLs, which I am. Below is my configuration and what the shape of the sidebar settings looks like:\r\n\n\n### Reproduction\n\n```ts\r\nexport default defineConfig({\r\n appearance: 'force-dark',\r\n base: '/',\r\n cleanUrls: true,\r\n description: 'Build emails with a delightful DX',\r\n head: [\r\n [\r\n 'link',\r\n {\r\n rel: 'shortcut icon',\r\n href: `data:image/svg+xml;charset=UTF-8,%3csvg width='126' height='113' viewBox='0 0 126 113' fill='none' xmlns='http://www.w3.org/2000/svg'%3e%3cpath fill-rule='evenodd' clip-rule='evenodd' d='M0.199951 50V109V113H4.19995H121.8H125.8V109V50H117.8V105H8.19995V50H0.199951Z' fill='%2364595C'/%3e%3cpath d='M0 53.429V47.4258L48.3069 22.8124V32.4176L11.2516 50.2773L11.5517 49.677V51.1778L11.2516 50.5775L48.3069 68.4372V78.0424L0 53.429Z' fill='%2364595C'/%3e%3cpath d='M79.4367 0L54.6832 92H46.582L71.3356 0H79.4367Z' fill='%2364595C'/%3e%3cpath d='M126 53.429L77.6931 78.0424V68.4372L114.748 50.5775L114.448 51.1778V49.677L114.748 50.2773L77.6931 32.4176V22.8124L126 47.4258V53.429Z' fill='%2364595C'/%3e%3c/svg%3e `\r\n }\r\n ]\r\n ],\r\n ignoreDeadLinks: true,\r\n markdown: {\r\n theme: {\r\n dark: 'slack-dark',\r\n light: 'slack-ochin'\r\n }\r\n },\r\n outDir: './dist',\r\n srcDir: 'markdown',\r\n themeConfig: {\r\n logo: '/logo.svg',\r\n // https://vitepress.dev/reference/default-theme-config\r\n nav: [\r\n { text: 'Documentation', link: '/docs/introduction' },\r\n { text: 'Quick Start', link: '/docs/quick-start' },\r\n { text: 'Email Samples', link: '/docs/samples' }\r\n ],\r\n sidebar,\r\n siteTitle: '',\r\n socialLinks: [\r\n { icon: 'discord', link: 'https://github.com/vuejs/vitepress' },\r\n { icon: 'github', link: 'https://github.com/shellscape/jsx-email' }\r\n ]\r\n },\r\n titleTemplate: 'JSX email • :title'\r\n});\r\n\r\n```\r\n\r\nAnd the sidebar:\r\n\r\n```ts\r\n[\r\n {\r\n text: 'Meat and Potatoes',\r\n items: [\r\n { link: '/docs/introduction', text: 'Introduction' },\r\n { link: '/docs/quick-start', text: 'Quick Start' },\r\n { link: '/docs/contributing', text: 'Contributing' }\r\n ]\r\n },\r\n {\r\n text: 'Components',\r\n items: [\r\n { link: '/docs/components/button', text: 'Button' },\r\n { link: '/docs/components/column', text: 'Column' },\r\n { link: '/docs/components/container', text: 'Container' },\r\n { link: '/docs/components/font', text: 'Font' },\r\n { link: '/docs/components/head', text: 'Head' },\r\n { link: '/docs/components/heading', text: 'Heading' },\r\n { link: '/docs/components/hr', text: 'Hr' },\r\n { link: '/docs/components/html', text: 'Html' },\r\n { link: '/docs/components/image', text: 'Image' },\r\n { link: '/docs/components/link', text: 'Link' },\r\n { link: '/docs/components/markdown', text: 'Markdown' },\r\n { link: '/docs/components/preview', text: 'Preview' },\r\n { link: '/docs/components/row', text: 'Row' },\r\n { link: '/docs/components/section', text: 'Section' },\r\n { link: '/docs/components/tailwind', text: 'Tailwind' },\r\n { link: '/docs/components/text', text: 'Text' }\r\n ]\r\n },\r\n {\r\n text: 'Core',\r\n items: [\r\n { link: '/docs/core/cli', text: 'Cli' },\r\n { link: '/docs/core/render', text: 'Render' }\r\n ]\r\n }\r\n]\r\n```\n\n### Expected behavior\n\nFollowing advice in other issues, I would have expected that using absolute urls in `link` would produce a behavior where the Next Page button would indeed show the name and url of the next page in the sidebar.\n\n### System Info\n\n```Text\nMacOS Ventura\r\nVitepress@latest\r\nNode v18\r\n\r\n(envinfo hangs on an M2)\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.",[2892,2895],{"name":2893,"color":2894},"bug: pending triage","e99695",{"name":2869,"color":2870},3031,"Next Page Always Shows First Page","2024-12-03T17:29:02Z","https://github.com/vuejs/vitepress/issues/3031",0.8219419,{"description":2902,"labels":2903,"number":2906,"owner":2872,"repository":2873,"state":2874,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### Is your feature request related to a problem? Please describe.\r\n\r\nSupport syntax highlight on inline code in docs.\r\n\r\nThe picture below is from an HTML code snippet using Prism and a syntax like this:\r\n```html\r\n\u003Ccode class=\"language-js\">if (user.actionsHistory[0].type ===\"undo\")\u003C/code>\r\n```\r\n\r\n\r\n\r\n\r\nAnd the picture below is the same writing with Vitepress:\r\n```md\r\n`if (user.actionsHistory.at(-1).type ===\"undo\")`\r\n```\r\n\r\n\r\n\r\n\r\nAs you see the Syntax Highlighting is gone. Could be cool to have an automatic inline Syntax Highlighting for md docs.\r\n\r\nHere is another example for a CSS code snippet. On the left using markdown and viteperss, and on the right, using html and prism:\r\n\r\n\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nThere'v been some suggestions before on vitepress: https://github.com/vuejs/vitepress/issues/1343 and vuepress: https://github.com/vuejs/vuepress/issues/1212 on how the syntax could look like. I personally do not have a preference. But I believe this syntax:\r\n```md\r\nAnd `if (someCondition === true)`{lang=js}\r\n```\r\nallows for future expansions:\r\n```md\r\nAnd `if (someCondition === true)`{lang=js,someFlag=false,someOtherFlag=true}\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\nHave not tried anything yet. Just faced this requirement while trying out vitepress. If I ever came up with a solution that did or did not work will share here.\r\n\r\n### Additional context\r\n\r\nThere was already 1 issue about this: https://github.com/vuejs/vitepress/issues/1343, but was closed as \"Not seeing any demand for this\". So I re-created this issue as a demand.\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.",[2904,2905],{"name":2866,"color":2867},{"name":2869,"color":2870},3093,"Feature Request: Inline Syntax Highlight","2025-03-02T18:10:32Z","https://github.com/vuejs/vitepress/issues/3093",0.8254636,{"description":2912,"labels":2913,"number":2917,"owner":2872,"repository":2873,"state":2918,"title":2919,"updated_at":2920,"url":2921,"score":2922},"There are certain edge cases where client-side filename sanitization doesn't work as expected and fails the builds / causes hydration issues.\r\n\r\nAnd handle these issues:\r\n\r\n- Remove leading underscore(s) from final assets\r\n- Handle special characters in filenames",[2914],{"name":2915,"color":2916},"build","377ba8",1472,"closed","Match server and client-side filename sanitization","2023-01-21T14:25:10Z","https://github.com/vuejs/vitepress/issues/1472",0.77315414,{"description":2924,"labels":2925,"number":2926,"owner":2872,"repository":2873,"state":2918,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Is your feature request related to a problem? Please describe.\n\nCurrently, when changing languages, the navbar links stay the same.\n\n### Describe the solution you'd like\n\nNavbar should have links based on the languages selected.\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.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.",[],1089,"Navbar for i18n","2023-01-21T14:28:59Z","https://github.com/vuejs/vitepress/issues/1089",0.80283815,{"description":2932,"labels":2933,"number":2935,"owner":2872,"repository":2873,"state":2918,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Is your feature request related to a problem? Please describe.\n\nI want user `h1` as my article outline, i can't use theme config to custom my outline\n\n### Describe the solution you'd like\n\nif i have config in my config.js\r\n```js\r\n themeConfig: {\r\n outline: [1,6] || 'all'\r\n}\r\n```\r\nthe title selector should like this\r\n```js\r\ndocument\r\n .querySelectorAll\u003CHTMLHeadingElement>('h1,h2, h3, h4, h5, h6') // include h1 title\r\n .forEach((el) => {\r\n if (el.textContent && el.id) {\r\n updatedHeaders.push({\r\n level: Number(el.tagName[1]),\r\n title: el.innerText.replace(/\\s+#\\s*$/, ''),\r\n link: `#${el.id}`\r\n })\r\n }\r\n })\r\n```\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.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.",[2934],{"name":2866,"color":2867},1529,"The levels of header to display in the outline can't support h1 title","2023-08-12T00:04:14Z","https://github.com/vuejs/vitepress/issues/1529",0.80546093,{"description":2941,"labels":2942,"number":2945,"owner":2872,"repository":2873,"state":2918,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the bug\r\n\r\nWhen markdown file is added `\u003Cscript>`, the custom component does not work properly and an error is reported with the error message `Hydration completed but contains mismatches.`.\r\n\r\n\r\n### Reproduction\r\n\r\nDemo repo: https://github.com/stevending1st/vitepress-hydration-bug-report\r\n\r\nHere are three markdown files, all of which introduce custom components.\r\n\r\n```md\r\n// test-1.md\r\n---\r\ntitle: ❌\r\n---\r\n\r\n\u003Cscript setup lang=\"ts\">\r\n// hello test\r\n\u003C/script>\r\n\r\n\u003CTestInfo />\r\n```\r\n\r\n```\r\n// test-2.md\r\n---\r\ntitle: ❌\r\n---\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport { ref } from \"vue\";\r\nimport yaml from \"yaml\";\r\nimport \"uno.css\";\r\n\u003C/script>\r\n\r\n\u003CTestInfo />\r\n```\r\n\r\n```\r\n// test-3.md\r\n---\r\ntitle: ❌\r\n---\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst data = 123;\r\n\u003C/script>\r\n\r\n\u003CTestInfo />\r\n\r\n```\r\n\r\nWhen I execute `pnpm dev`(`vitepress dev website`), accessing `/test-1`, `/test-2`, `/test-3` works fine.\r\n\r\nWhen I execute `pnpm build && pnpm preview`(`vue-tsc && vitepress build website && vitepress preview website`), visit `/test-1`, `/test-2`, `/test-3`, my custom component does not work properly and the F12 console reports `Hydration completed but contains mismatches.`.\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nWhen I add the valid `\u003Cscript>` and execute `vue-tsc && vitepress build website && vitepress preview website`, the custom components will display normally and the console will not report an error.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.22000\r\n CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H\r\n Memory: 1.13 GB / 15.73 GB\r\n Binaries:\r\n Node: 16.17.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.15.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22000.120.0), Chromium (109.0.1518.78)\r\n Internet Explorer: 11.0.22000.120\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.32 => 1.0.0-alpha.32\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.",[2943,2944],{"name":2893,"color":2894},{"name":2869,"color":2870},1918,"Warn `Hydration completed but contains mismatches.` and Custom components are not rendered","2023-08-11T00:04:12Z","https://github.com/vuejs/vitepress/issues/1918",0.8075407,{"description":2951,"labels":2952,"number":2953,"owner":2872,"repository":2873,"state":2918,"title":2954,"updated_at":2955,"url":2956,"score":2957},"\u003Cimg width=\"774\" alt=\"image\" src=\"https://user-images.githubusercontent.com/49258868/220234326-c41845d3-fb60-4f10-98f8-41b998106080.png\">\r\n\r\nCould you please tell me how to add such an outer box style to the code section in the theme",[],1965,"How to achieve the effect","2023-02-21T06:03:05Z","https://github.com/vuejs/vitepress/issues/1965",0.8087844,{"description":2959,"labels":2960,"number":2962,"owner":2872,"repository":2873,"state":2918,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Describe the bug\n\n* demo \r\n\r\n\r\n* demo in vitepress\r\ncontaminated element-plus css\r\n\r\n\n\n### Reproduction\n\nvitepress contaminated element-plus css\n\n### Expected behavior\n\nkeep the original style\n\n### System Info\n\n```shell\n--\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2961],{"name":2893,"color":2894},2266,"vitepress contaminated element-plus css","2023-04-29T00:03:39Z","https://github.com/vuejs/vitepress/issues/2266",0.81636024,["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fFvfuV-LljTKgkVeFzAibRhFu7cDE6w5JOh7mCJ7y7F4":-1},"/vuejs/vitepress/1421"]