\r\n \u003C/template>\r\n \u003C/VPTeamPageSection>\r\n\u003C/VPTeamPage>\r\n```\n\n### Expected behavior\n\n\r\n\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11\r\n Binaries:\r\n Node: 20.10.0\r\n Yarn: 1.22.19\r\n npm: 10.5.0\r\n pnpm: 8.15.5\r\n Browsers:\r\n Edge: Chromium (123.0.2420.81)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: 1.0.0-rc.43\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.",[2865,2868],{"name":2866,"color":2867},"theme","0754FB",{"name":2869,"color":2870},"stale","ededed",3769,"vuejs","vitepress","open","Support centering members in VPTeamPage","2025-03-02T18:09:24Z","https://github.com/vuejs/vitepress/issues/3769",0.71748966,{"description":2880,"labels":2881,"number":2883,"owner":2872,"repository":2873,"state":2874,"title":2884,"updated_at":2885,"url":2886,"score":2887},"### Is your feature request related to a problem? Please describe.\r\n\r\nThis is especially useful if user has a lot of content and each stage took relatively long.\r\n\r\n_**People love seeing progress.**_\r\n\r\n### Describe the solution you'd like\r\n\r\nCan either be a square bracket like `[Completed/Total]` or a progress bar.\r\n\r\nFor simplicity I would recommend the prior.\r\n\r\nExample:\r\n\r\n```plaintext\r\n✓ building client + server bundles - 23.69 seconds\r\n⠹ rendering pages [349/1382]\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nI am currently working on it. Generally its going to expose a handler to each task so they can update their progress. It is optional.\r\n\r\nPlease feel free to leave comments.\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],{"name":2869,"color":2870},3384,"[build] add progress indication for `task()`","2025-03-02T18:10:03Z","https://github.com/vuejs/vitepress/issues/3384",0.7745888,{"description":2889,"labels":2890,"number":2895,"owner":2872,"repository":2873,"state":2874,"title":2896,"updated_at":2897,"url":2898,"score":2899},"### Describe the bug\n\n搜索不到内容\n\n### Reproduction\n\n中文内容\n\n### Expected behavior\n\n\r\n\n\n### System Info\n\n```Text\nno\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.",[2891,2894],{"name":2892,"color":2893},"help wanted","008672",{"name":2869,"color":2870},4049,"Better default minisearch tokenizer for Chinese documents","2025-03-02T18:08:57Z","https://github.com/vuejs/vitepress/issues/4049",0.7873935,{"description":2901,"labels":2902,"number":2906,"owner":2872,"repository":2873,"state":2907,"title":2908,"updated_at":2909,"url":2910,"score":2911},"I trying to create a dropdown with versions of my app, and remove (or add) elements based on this version. Anyone have example how to make it? or maybe its a proposal to make default in vite",[2903],{"name":2904,"color":2905},"duplicate","cfd3d7",1550,"closed","[Question] How to create a dropdown version?","2023-01-21T14:22:48Z","https://github.com/vuejs/vitepress/issues/1550",0.7519395,{"description":2913,"labels":2914,"number":2921,"owner":2872,"repository":2873,"state":2907,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Describe the bug\r\n\r\nIf I reference a PDF from a Markdown file like so:\r\n\r\n\r\n```md\r\nPlease see this [document](./doc.pdf)\r\n```\r\n\r\nAnd the `doc.pdf` lives in the same directory as the Markdown file, Vitepress does not process the PDF & add it to the `assetsDir` during build, resulting in `404` when the site is deployed. \r\n\r\nThe documentation on [Referencing Static Assets](https://vitepress.dev/guide/asset-handling#referencing-static-assets) seems to suggest it should. Am I missing something or is this not supported?\r\n\r\n(Right now I'm working round this by placing the file in the `/public` directory)\r\n\r\n### Reproduction\r\n\r\nExplained above.\r\n\r\n### Expected behavior\r\n\r\nI would expect the PDF to be available as an asset.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\r\n CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz\r\n Memory: 47.97 GB / 62.54 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 20.11.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 10.2.4 - /usr/bin/npm\r\n pnpm: 8.6.12 - ~/.local/share/pnpm/pnpm\r\n Browsers:\r\n Chrome: 121.0.6167.139\r\n Chromium: 121.0.6167.85\r\n npmPackages:\r\n vitepress: 1.0.0-rc.40 => 1.0.0-rc.40\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.",[2915,2918],{"name":2916,"color":2917},"docs","0075ca",{"name":2919,"color":2920},"contribution welcome","11E4B8",3535,"PDF not included in assets directory","2024-03-07T00:03:35Z","https://github.com/vuejs/vitepress/issues/3535",0.75298613,{"description":2927,"labels":2928,"number":2929,"owner":2872,"repository":2873,"state":2907,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Is your feature request related to a problem? Please describe.\n\nI'm running into a problem with how I'm using frontmatter and Vue components in a markdown file. Before getting into this, I think this issue should be labeled \"Question\" rather than Feature Request. \r\n\r\nI am using frontmatter to list paths to image files. The list is then passed to an `ImageGallery` component where styling and click events (lightboxes) happen. \r\n\r\n```md\r\n---\r\ntitle: Section One\r\nitems:\r\n - \"./image-01.jpg\"\r\n - \"./image-02.jpg\"\r\n---\r\n\r\n\u003Cscript setup>\r\nimport ImageGallery from \"../components/ImageGallery.vue\"\r\n\u003C/script>\r\n\r\n# {{ $frontmatter.title }}\r\n\r\n\u003CImageGallery :items=\"$frontmatter.items\" />\r\n```\r\n\r\nThis works fine in development, but after running `build`, and `preview`, the image files 404. This makes sense because the image files are not included in the `dist/`. \r\n\r\nSo, with the way that vitepress [handles assets](https://vitepress.vuejs.org/guide/asset-handling), is it possible to use images in this way; a list of paths defined in frontmatter. Or do all images have to be defined like a standard markdown image? \r\n\r\n```md\r\n\r\n```\r\n\r\nIt would be super awesome to create a reusable gallery/lightbox component vs having to list out lots of images in md. \r\n\r\n```md\r\n\r\n\r\n\r\n\r\n```\n\n### Describe the solution you'd like\n\nI'm unsure how we could use frontmatter to include paths-to-images in the final dist—maybe checking each list item to see if it is a string and the file extension? \r\n\r\n\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\nHere's a link to the example repo: [https://github.com/drewalth/vitepress-image-gallery-frontmatter.git](https://github.com/drewalth/vitepress-image-gallery-frontmatter.git).\r\n\r\nI'm sorry if this is a duplicate...\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.",[],1909,"Use Frontmatter for List of Paths to Images ","2023-02-17T00:04:38Z","https://github.com/vuejs/vitepress/issues/1909",0.7745066,{"description":2935,"labels":2936,"number":2937,"owner":2872,"repository":2873,"state":2907,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Is your feature request related to a problem? Please describe.\n\nLet's say we got a folder structure like this:\r\n\r\n\r\n└─ foo\r\n ├─ 1.0.0.md\r\n ├─ 2.0.0.md\r\n └─ 3.0.0.md\r\n\r\nRight now we would have routes like:\r\n `/foo/1.0.0.html`\r\n `/foo/2.0.0.html`\r\n `/foo/3.0.0.html`\r\n\r\nI'd like to also have a route or alias like the following: `/foo/latest` which will point to the latest version (this can all be determined on build time by looking at the file, I already have a function that gives me the latest \"route\", in this case `/foo/3.0.0.html`.\r\n\r\nHow can I make this `/foo/latest` route exist and be an alias to the one I wanted?\n\n### Describe the solution you'd like\n\nAllow us to define route aliases or redirects\n\n### Describe alternatives you've considered\n\nI've tried with rewrites but that allowed me to make the latest version redirected to /latest instead. I want the reverse.\n\n### Additional context\n\nIf this is not something you think vitepress should have because it's not SSG friendly (there is no latest.html file) then I understand.\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.",[],2922,"Route Alias or Redirect","2023-09-16T00:04:02Z","https://github.com/vuejs/vitepress/issues/2922",0.7760094,{"description":2943,"labels":2944,"number":2947,"owner":2872,"repository":2873,"state":2907,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\nWhen sidebar is not present, the page is not scrolled and outline is scrolled down, it overflows the navbar.\r\n\r\n \r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-v81ufa\r\n\r\n1. Make sure width is high enough so that outline is shown\r\n2. Without scrolling the main page content hover over the outline and scroll down\r\n3. Observe that the outline overflows the navbar\n\n### Expected behavior\n\nOutline is clipped when over navbar in the same way when sidebar is present.\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz\r\n Memory: 45.66 GB / 63.92 GB\r\n Binaries:\r\n Node: 18.2.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.5 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 9.6.6 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.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.",[2945,2946],{"name":2866,"color":2867},{"name":2919,"color":2920},2442,"Outline overflows navbar when sidebar not present","2023-08-16T00:04:22Z","https://github.com/vuejs/vitepress/issues/2442",0.77744454,{"description":2953,"labels":2954,"number":2955,"owner":2872,"repository":2873,"state":2907,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Is your feature request related to a problem? Please describe.\n\nI want to vitepress cli support this feature to set some path for vitepress configuration. I search the vitepress docs and found nothing about it.\r\nHonestly, path \"./vitepress/config.ts\" is ugly to me.\n\n### Describe the solution you'd like\n\nLike that: vitepress --config yourConfigPath dev\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.",[],2084,"How can I change default config path, like /projectRoot/config/vitepress.config.ts.","2023-03-22T00:03:23Z","https://github.com/vuejs/vitepress/issues/2084",0.778535,{"description":2961,"labels":2962,"number":2966,"owner":2872,"repository":2873,"state":2907,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Describe the bug\r\n\r\nDefault theme's `VPFlyout` has these css:\r\n\r\n```css\r\n.VPFlyout:hover .menu,\r\n.button[aria-expanded=\"true\"] + .menu {\r\n opacity: 1;\r\n visibility: visible;\r\n transform: translateY(0);\r\n}\r\n\r\n.button[aria-expanded=\"false\"] + .menu {\r\n opacity: 0;\r\n visibility: hidden;\r\n transform: translateY(0);\r\n}\r\n```\r\n\r\nAccording to [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity), the selector ` ` and `+` have the same specificity, which means the rule that comes next will override the rule that comes first. The result is, when JavaScript is disabled, the `aria-expanded` property will keep as `false`, and the contents of `VPFlyout` will never show.\r\n\r\n### Reproduction\r\n\r\nJust go to [the official docs site](https://vitepress.dev/), disable JavaScript. Move mouse cursor over any `VPFlyout` components.\r\n\r\n### Expected behavior\r\n\r\nThe contents of `VPFlyout` should show with no JavaScript.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 6.10 Arch Linux\r\n CPU: (16) x64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz\r\n Memory: 22.07 GB / 31.13 GB\r\n Container: Yes\r\n Shell: 3.7.1 - /usr/bin/fish\r\n Binaries:\r\n Node: 20.17.0 - ~/.nix-profile/bin/node\r\n npm: 10.8.2 - ~/.nix-profile/bin/npm\r\n pnpm: 9.9.0 - ~/.nix-profile/bin/pnpm\r\n bun: 1.1.29 - /usr/bin/bun\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.",[2963],{"name":2964,"color":2965},"bug: pending triage","e99695",4224,"Default theme's `VPFlyout` does not show without JavaScript","2024-10-01T04:45:56Z","https://github.com/vuejs/vitepress/issues/4224",0.77961355,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4aZvkAdWqEz4BftcOMbim-oFfNq19fumtaSTJvFB3HQ":-1},"/vuejs/vitepress/2863"]