\n\n\u003Cimg width=\"308\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0e1beb6b-d06b-436c-b106-c924fead87ab\" />\n\n\u003Cimg width=\"931\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/aef6f71a-fa28-4b7c-b512-e6386e18159a\" />\n\n### Describe the solution you'd like\n\nIn my [pull request](https://github.com/vuejs/vitepress/pull/4630), I've introduced custom components that can be overridden in the `enhanceApp` function. In these custom components, I can add custom logic for rendering text, such as using the Vue compile function. \n\nAdditionally, I added a flag to skip the title update, allowing for custom logic implementation. \n\nPlease also see my PR: [https://github.com/vuejs/vitepress/pull/4630](https://github.com/vuejs/vitepress/pull/4630).\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.",[],4637,"vuejs","vitepress","open","Sidenav Components / Skip title update","2025-03-20T12:17:14Z","https://github.com/vuejs/vitepress/issues/4637",0.6938676,{"description":2876,"labels":2877,"number":2881,"owner":2868,"repository":2869,"state":2882,"title":2883,"updated_at":2884,"url":2885,"score":2886},"### Describe the bug\r\n\r\nwhen I update the version to `\"vitepress\": \"^1.0.0-alpha.63\",` , and run `vitepress dev docs`, The Aside component is render nothing\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nupdate the vitepress version to `\"vitepress\": \"^1.0.0-alpha.63\",`\r\n\r\nrun `vitepress dev docs`\r\n\r\n`config.js`\r\n```\r\nimport { defineConfigWithTheme } from 'vitepress';\r\nimport vueJsx from '@vitejs/plugin-vue-jsx';\r\nimport baseConfig from '@vue/theme/config';\r\nimport { demoBlockPlugin } from 'vitepress-theme-demoblock';\r\nimport path from 'path';\r\n\r\nimport { i18n, nav, sidebar } from './themeConfig/index';\r\n\r\nexport default defineConfigWithTheme({\r\n extends: baseConfig,\r\n lang: 'zh-CN',\r\n title: 'SinoGear Vue',\r\n description: '',\r\n srcDir: './src',\r\n scrollOffset: 'header',\r\n ignoreDeadLinks: true,\r\n head: [['meta', { name: 'theme-color', content: '#3c8772' }]],\r\n themeConfig: {\r\n nav,\r\n sidebar,\r\n appearance: false, // 开启 light/dark 模式\r\n // Placeholder of the i18n config for @vuejs-translations.\r\n i18n,\r\n },\r\n\r\n markdown: {\r\n config(md) {\r\n md.use(demoBlockPlugin, {\r\n cssPreprocessor: 'less',\r\n scriptImports: [\r\n \"import * as AntDesignVue from 'ant-design-vue'\",\r\n ],\r\n scriptReplaces: [\r\n {\r\n searchValue: /import ({.*}) from 'ant-design-vue'/g,\r\n replaceValue: (s, s1) => `const ${s1} = AntDesignVue`\r\n },\r\n ]\r\n });\r\n }\r\n },\r\n\r\n vite: {\r\n server: {\r\n host: true,\r\n port: 3001,\r\n fs: {\r\n // for when developing with locally linked theme\r\n allow: ['../..']\r\n }\r\n },\r\n build: {\r\n chunkSizeWarningLimit: Infinity\r\n },\r\n json: {\r\n stringify: true\r\n },\r\n ssr: {\r\n noExternal: ['@wangeditor/editor', '@wangeditor/editor-for-vue', 'ant-design-vue', '@ant-design/icons-vue', '@babel/runtime']\r\n },\r\n plugins: [vueJsx()],\r\n css: {\r\n preprocessorOptions: {\r\n less: {\r\n javascriptEnabled: true\r\n }\r\n }\r\n }\r\n },\r\n\r\n vue: {\r\n reactivityTransform: path.resolve(__dirname, 'src')\r\n }\r\n});\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nrender aside component\r\n\r\n### System Info\r\n\r\n\r\n`packages.json`\r\n```shell\r\n\r\n\"@babel/plugin-syntax-jsx\": \"^7.18.6\",\r\n \"@vitejs/plugin-vue\": \"^4.0.0\",\r\n \"@vitejs/plugin-vue-jsx\": \"^3.0.0\",\r\n \"@vue/babel-plugin-jsx\": \"^1.1.1\",\r\n \"@vue/compiler-sfc\": \"^3.0.4\",\r\n \"conventional-changelog-cli\": \"^2.1.0\",\r\n \"cross-env\": \"^7.0.2\",\r\n \"del\": \"^6.0.0\",\r\n \"gulp\": \"^4.0.2\",\r\n \"gulp-babel\": \"^8.0.0\",\r\n \"highlight.js\": \"^10.4.1\",\r\n \"less\": \"^4.1.2\",\r\n \"lint-staged\": \"^13.0.3\",\r\n \"prettier\": \"^2.7.1\",\r\n \"rimraf\": \"^3.0.0\",\r\n \"transliteration\": \"^2.2.0\",\r\n \"vitepress\": \"^1.0.0-alpha.63\",\r\n \"vitepress-plugin-search\": \"^1.0.4-alpha.17\",\r\n \"vitepress-theme-demoblock\": \"^2.0.0\"\r\n```\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.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2878],{"name":2879,"color":2880},"need more info","bdbefc",2157,"closed","The Aside component is render nothing","2023-04-05T00:04:02Z","https://github.com/vuejs/vitepress/issues/2157",0.673988,{"description":2888,"labels":2889,"number":2893,"owner":2868,"repository":2869,"state":2882,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### Describe the bug\n\nindex.md not support markdown\n\n### Reproduction\n\n\"I'm encountering an issue with VitePress where Markdown syntax in my index.md file doesn't seem to apply the expected styles on the homepage, whereas in VuePress, this works as anticipated. For instance, if I wish to include some introductory text on the main page and then guide users to the navigation bar, it appears that I need to manually write the CSS styles. Why can't I utilize Markdown for styling in this case?\"\n\n### Expected behavior\n\n\"I'm encountering an issue with VitePress where Markdown syntax in my index.md file doesn't seem to apply the expected styles on the homepage, whereas in VuePress, this works as anticipated. For instance, if I wish to include some introductory text on the main page and then guide users to the navigation bar, it appears that I need to manually write the CSS styles. Why can't I utilize Markdown for styling in this case?\"\n\n### System Info\n\n```Text\n\"I'm encountering an issue with VitePress where Markdown syntax in my index.md file doesn't seem to apply the expected styles on the homepage, whereas in VuePress, this works as anticipated. For instance, if I wish to include some introductory text on the main page and then guide users to the navigation bar, it appears that I need to manually write the CSS styles. Why can't I utilize Markdown for styling in this case?\"\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.",[2890],{"name":2891,"color":2892},"bug: pending triage","e99695",3409,"index.md","2024-01-13T00:04:51Z","https://github.com/vuejs/vitepress/issues/3409",0.6800151,{"description":2899,"labels":2900,"number":2902,"owner":2868,"repository":2869,"state":2882,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Describe the bug\r\n\r\nThe `\u003CContent />` component wraps the code with a \"position: relative\" styled div. \r\n\r\n\u003Cimg width=\"656\" alt=\"Screenshot 2023-07-30 at 9 43 37 PM\" src=\"https://github.com/vuejs/vitepress/assets/90354202/a7f83520-edc3-415d-b851-2487693e1ba9\">\r\n\r\n\r\n### Reproduction\r\n\r\nThe \u003CContent /> component wraps the code with a \"position: relative\" styled div. \r\n\r\n### Expected behavior\r\n\r\nThere is no documentation on how to disable that from happening and it shouldn't do that in the first place anyway. \r\n\r\n### System Info\r\n\r\n```sh\r\nv1.0.0-beta.7\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.",[2901],{"name":2891,"color":2892},2712,"The \u003CContent /> component wraps the code with a \"position: relative\" styled div.","2023-08-11T00:04:38Z","https://github.com/vuejs/vitepress/issues/2712",0.68513227,{"description":2908,"labels":2909,"number":2911,"owner":2868,"repository":2869,"state":2882,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Describe the bug\n\nChanged the config file a bit and moved directory's around and then the aside started to be intruding the screen. \n\nIt was working fine before, and it works fine when I run `npm run docs:dev` but when I build and run a preview this issue happens.\n\n\n\n### Reproduction\n\nNo idea\n\n### Expected behavior\n\nThe aside should not be on the doc. It should be on the right hand side, like what the vitepress docs looks like.\n\n\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (20) x64 13th Gen Intel(R) Core(TM) i9-13900H\n Memory: 17.98 GB / 31.64 GB\n Binaries:\n Node: 22.12.0 - C:\\Program Files\\nodejs\\node.EXE\n Yarn: 1.22.22 - C:\\Program Files\\nodejs\\yarn.CMD\n npm: 10.9.0 - C:\\Program Files\\nodejs\\npm.CMD\n Browsers:\n Edge: Chromium (131.0.2903.99)\n Internet Explorer: 11.0.26100.1882\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.",[2910],{"name":2891,"color":2892},4534,"Aside is intruding the page","2025-02-09T04:41:56Z","https://github.com/vuejs/vitepress/issues/4534",0.69696164,{"description":2917,"labels":2918,"number":2920,"owner":2868,"repository":2869,"state":2882,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Is your feature request related to a problem? Please describe.\n\nImagine the use case:\r\n\r\nThere are some settings on the left side (just like `vuejs.org`'s API style switch), but I want it to show/hide some `h2` or `h3`, or say, those heading elements which will be in the aside.\r\n\r\nBy wrapping entire `h2` or `h3` parts by a `\u003Cdiv>` and using classes on the root element to control their visibility based on the value of settings. However, currently, the aside content won't update in this case.\r\n\r\n---\r\n\r\nIf you don't want this to be part of the default theme, please inform me and close this issue, Thanks.\n\n### Describe the solution you'd like\n\nI'm here to gather whether you want this to be a feature in the default theme, as I already implemented it by overriding internal files (that's a bit frustrating honestly) and it's working well for me, so I can raise the MR if you would like to accept this feature as part of the default theme.\r\n\r\nMy implementation in high-level:\r\n1. In those aside components (i.e. `VPDocAsideOutline.vue`, `VPDocOutlineDropdown.vue` and `VPLocalNav.vue`\r\n2. Using `IntersectionObserver` to observe the visibility against root (`\u003Chtml>`)\r\n3. Once change is detected, regenerate the headers and cleanup + apply step 2 again.\r\n\r\nPlease feel free to advise if you have a better approach.\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.",[2919],{"name":2879,"color":2880},2686,"✨Feature: Re-generate aside content when visbility of anchor headings change","2023-08-11T00:04:06Z","https://github.com/vuejs/vitepress/issues/2686",0.70151824,{"description":2926,"labels":2927,"number":1992,"owner":2868,"repository":2869,"state":2882,"title":2929,"updated_at":2930,"url":2931,"score":2932},"\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\nA clear and concise description of what the bug is.\r\n\r\n1. Expect \r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n\r\n1. Create `index.md` file with a few headings\r\n1. Sidebar auto is turned on\r\n1. Add new headings (h2s or h3s) to `index.md` file\r\n1. Save file\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\nSidebar should rerender with the appropriate headings.\r\n\r\n**System Info**\r\n- vitepress version: v0.4.0\r\n- vite version: v1.0.0-beta.1\r\n- Node version: v12.16.1\r\n- OS version: macOS 10.15.5\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2928],{"name":2891,"color":2892},"Sidebar does not re-render based on new content in markdown","2023-01-21T16:23:57Z","https://github.com/vuejs/vitepress/issues/32",0.7053115,{"description":2934,"labels":2935,"number":2939,"owner":2868,"repository":2869,"state":2882,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Describe the bug\n\nWhen the default theme is used, when the sidebar configuration is greater than or equal to four layers, the navigation menu title style of the content md file parsing is missing\r\n\r\n\n\n### Reproduction\n\n\r\n![Uploading image.png…]()\r\n\n\n### Expected behavior\n\nRegardless of whether the parsed style of several layers of content is correct, or the level is configurable\n\n### System Info\n\n```shell\nvitepress:0.19.2\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\n- [X] Read the [docs](https://vitepress.vuejs.org/).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2936],{"name":2937,"color":2938},"theme","0754FB",409,"When the sidebar configuration exceeds four levels, the title style generated by parsing the content is missing","2023-01-21T16:04:06Z","https://github.com/vuejs/vitepress/issues/409",0.70617634,{"description":2945,"labels":2946,"number":2950,"owner":2868,"repository":2869,"state":2882,"title":2951,"updated_at":2952,"url":2953,"score":2954},"I'd like to only have a custom NavLinks component while keeping the default vitepress theme. Next I looked at the NavBar although also my version doesn't override. Any help in the right direction would be great.\r\n\r\ndocs/.vitepress/config.js\r\n\r\n```\r\nimport Theme from 'vitepress/theme'\r\nimport '../../assets/vars.css'\r\nimport NavBar from './Mynav.vue'\r\n\r\nconst MyTheme = {...Theme, Layout: {...Theme.Layout, NavBar}}\r\n\r\nexport default {\r\n ...MyTheme,\r\n NotFound: () => 'custom 404',\r\n enhanceApp({app, router, siteData}) {\r\n\r\n },\r\n}\r\n```\r\n ",[2947],{"name":2948,"color":2949},"docs","0075ca",235,"Extending the vitepress theme","2023-03-18T00:04:16Z","https://github.com/vuejs/vitepress/issues/235",0.70752,{"description":2956,"labels":2957,"number":2959,"owner":2868,"repository":2869,"state":2882,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Describe the bug\n\nThe aside's outline marker will have an annoying flick when navigating towards above. All `vitepress` sites seems have this problem.\r\n\r\nThe video should be enough to demo the issue. (Sorry for the bad quality)\n\n### Reproduction\n\nhttps://github.com/vuejs/vitepress/assets/45784210/d21095b6-a769-45c5-9119-0fc88f041c3f\n\n### Expected behavior\n\nNo flick\n\n### System Info\n\n```sh\nChrome 114\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.",[2958],{"name":2937,"color":2938},2665,"🐞Bug: `aside`'s outline marker is flicking when navigating towards above","2023-08-15T00:04:22Z","https://github.com/vuejs/vitepress/issues/2665",0.71095693,["Reactive",2965],{},["Set"],["ShallowReactive",2968],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKpJEzxFlxaXsJQfBiJcgdiPfMi3z0U7GB7c0p7SJKTc":-1},"/vuejs/vitepress/3251"]