\r\n\u003C/template>\r\n\r\n\u003Cstyle>\r\n .link--active {\r\n font-weight: bold;\r\n }\r\n\u003C/style>\r\n\r\n```\n\n### Expected behavior\n\nShould be the same as in dev mode: When loading the page the first time:\r\n\r\n- The text part `{{isActiveRoute(href)? 'active': 'inactive'}}` is updated ✔️\r\n- The `:class=\"{'link--active': isActiveRoute(href)}\"` is updated on first render. ✔️\r\n\r\nThe HTML output on build on first render should be same as in dev mode:\r\n\r\n```html\r\n\u003Cul>\r\n \u003Cli>\u003Ca href=\"/\" class=\"link--active\">active: Home\u003C/a>\u003C/li>\r\n \u003Cli>\u003Ca href=\"/markdown-examples.html\" class=\"\">inactive: Markdown Examples\u003C/a>\u003C/li>\r\n \u003Cli>\u003Ca href=\"/api-examples.html\" class=\"\">inactive: API Examples\u003C/a>\u003C/li>\r\n\u003C/ul>\r\n```\r\n\r\n\r\n\n\n### System Info\n\n```Text\nError can also be reproduced on vercel.\r\n\r\nLocal install\r\n\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (4) x64 Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz\r\n Memory: 1.28 GB / 7.92 GB\r\n Binaries:\r\n Node: 18.17.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.18 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 9.6.7 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 8.3.1 - C:\\Program Files\\nodejs\\pnpm.CMD\r\n Browsers:\r\n Chrome: 116.0.5845.188\r\n Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.31)\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.14 => 1.0.0-rc.14\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.",[2920],{"name":2921,"color":2922},"has-workaround","1B4515",2995,"Build & Dev behaves differently: Build does not update reactive class name on the first page render","2023-09-30T00:04:15Z","https://github.com/vuejs/vitepress/issues/2995",0.72924954,{"description":2929,"labels":2930,"number":2934,"owner":2871,"repository":2872,"state":2873,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Describe the bug\n\nEven when you set theme.outline = false vitepress still adds class has-aside and therefore content is unnecessary constrained to narrow space\n\n### Reproduction\n\nSet theme.outline to false to hide aside. Even thou it's not displayed it still ocupies space and therefore width of .VPDoc container is the same as with theme.outline\n\n### Expected behavior\n\nWhen aside is hidden it should free up space\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz\r\n Memory: 5.57 GB / 15.80 GB\r\n Binaries:\r\n Node: 16.16.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.11 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 9.2.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (109.0.1518.78)\r\n Internet Explorer: 11.0.19041.1566\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2931],{"name":2932,"color":2933},"theme","0754FB",1915,"support disabling aside in themeConfig","2023-02-20T00:04:34Z","https://github.com/vuejs/vitepress/issues/1915",0.72954607,{"description":2940,"labels":2941,"number":2942,"owner":2871,"repository":2872,"state":2873,"title":2943,"updated_at":2944,"url":2945,"score":2946},"After configuring according to the document, after clicking the search, \"#VPContent\" will be added after the original link and will not jump to the search result, as shown in the figure.\r\n\u003Cimg src=https://cdn.jsdelivr.net/gh/vanhiupun/pic@1.0/img/202309112316868.png width=60% />\r\n```yaml\r\n // algolia搜索\r\n search: {\r\n provider: 'algolia',\r\n options: {\r\n appId: 'xxxxx',\r\n apiKey: 'xxxxx',\r\n indexName: 'xxxxxx'\r\n }\r\n },",[],2944,"\"Algolia Search\" cannot jump to the page","2023-09-21T00:04:13Z","https://github.com/vuejs/vitepress/issues/2944",0.73001367,{"description":2948,"labels":2949,"number":2951,"owner":2871,"repository":2872,"state":2873,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the bug\r\n\r\n[VPMenuLink](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/components/VPMenuLink.vue) does not handle regex for `activeMatch`.\r\n\r\n### Reproduction\r\n\r\nPlease see this [StackBlitz](https://stackblitz.com/edit/vite-arkwyp?file=docs/.vitepress/config.ts):\r\n\r\n1. Click `Dropdown Menu > Item A`. The `Item A` of the `Dropdown Menu` is active.\r\n2. Click `Next Page` to go to second page. The `Item A` of the `Dropdown Menu` is inactive.the \r\n\r\n### Expected behavior\r\n\r\nThe `Item A` in the Nav should be active on both pages.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 13.0.1\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz\r\n Memory: 26.19 MB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.12.0 - ~/.config/nvm/versions/node/v18.12.0/bin/node\r\n Yarn: 1.22.19 - ~/.config/nvm/versions/node/v18.12.0/bin/yarn\r\n npm: 8.19.2 - ~/.config/nvm/versions/node/v18.12.0/bin/npm\r\n Browsers:\r\n Chrome: 108.0.5359.124\r\n Safari: 16.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.35 => 1.0.0-alpha.35 \r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI think we should add the third parameter to the function `isActive` in the component `VPMenuLink` because it handles the regex.\r\n\r\nhttps://github.com/vuejs/vitepress/blob/01ac57918767f44a0757414316e67072399ffb6d/src/client/theme-default/components/VPMenuLink.vue#L16\r\n\r\nJust like `VPNavBarMenuGroup`:\r\n\r\nhttps://github.com/vuejs/vitepress/blob/01ac57918767f44a0757414316e67072399ffb6d/src/client/theme-default/components/VPNavBarMenuGroup.vue#L21\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.",[2950],{"name":2882,"color":2883},1771,"VPMenuLink does not handle regex for activeMatch","2023-01-21T14:16:46Z","https://github.com/vuejs/vitepress/issues/1771",0.73015594,{"description":2957,"labels":2958,"number":2960,"owner":2871,"repository":2872,"state":2873,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Describe the bug\n\n\r\n\r\n\r\nsame happens when there's another `base: '/section2/',` in sidebar\n\n### Reproduction\n\nconfig:\r\n```ts\r\nexport default defineConfig({\r\n\r\n...\r\n\r\n sidebar: [\r\n {\r\n base: '/section/',\r\n items: [\r\n { text: 'First', link: '/first' },\r\n { text: 'Second', link: '/second' },\r\n { text: 'Third', link: '/third' },\r\n ]\r\n },\r\n ],\r\n\r\n...\r\n```\r\n\r\nfolder structure:\r\n\r\n\r\n\n\n### Expected behavior\n\n\r\n\r\n(like without the base link and md files stored in parent folder)\n\n### System Info\n\n```Text\nrc20, windows\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.",[2959],{"name":2882,"color":2883},3010,"bottom page navigation link always directs to first page when using base URLs for sidebar","2023-10-02T00:04:34Z","https://github.com/vuejs/vitepress/issues/3010",0.73218,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fo7Rt8xFwa-xVH-gpnnqKB5bUeg0PsfjgOv2-bKddpKo":-1},"/vuejs/vitepress/2207"]