\r\n\u003Cscript setup>\r\nimport Test from './Test.vue';\r\n\u003C/script>\r\n```\r\n\n\n### Reproduction\n\ngo to chrome developer tool and console tab to view error details\n\n### Expected behavior\n\nI should able read the custom variable chapter & topic variable \n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.13 Ubuntu 21.10 21.10 (Impish Indri)\r\n CPU: (4) x64 Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz\r\n Memory: 558.27 MB / 5.71 GB\r\n Container: Yes\r\n Shell: 5.8 - /usr/bin/zsh\r\n Binaries:\r\n Node: 14.19.0 - /usr/bin/node\r\n Yarn: 1.22.17 - /usr/local/bin/yarn\r\n npm: 7.17.0 - /usr/local/bin/npm\r\n Browsers:\r\n Brave Browser: 98.1.35.101\r\n Firefox: 97.0.1\r\n \"devDependencies\": {\r\n \"postcss\": \"^8.4.6\",\r\n \"sass\": \"^1.49.8\",\r\n \"stylus\": \"^0.56.0\",\r\n \"vitepress\": \"^0.22.2\",\r\n \"tailwindcss\": \"^3.0.23\"\r\n },\r\n \"dependencies\": {\r\n \"autoprefixer\": \"^10.4.2\"\r\n },\r\n \"postcss\": {\r\n \"plugins\": {\r\n \"tailwindcss\": {},\r\n \"autoprefixer\": {}\r\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2899],{"name":2900,"color":2901},"bug: pending triage","e99695",550,"How to read sitedata and pagedata inside vue component with default theme","2023-01-21T16:20:05Z","https://github.com/vuejs/vitepress/issues/550",0.7404827,{"description":2908,"labels":2909,"number":2910,"owner":2869,"repository":2870,"state":2883,"title":2911,"updated_at":2912,"url":2913,"score":2914},"Ref: https://vuepress.vuejs.org/theme/default-theme-config.html#prev-next-links\r\n\r\nThis one may be tricky since VitePress doesn't include the whole site's page metadata (for bundle size considerations). We may need to extract this information at build time and include it directly in each individual page's metadata (`$page`)",[],43,"Prev / Next links","2023-01-21T16:25:34Z","https://github.com/vuejs/vitepress/issues/43",0.743019,{"description":2916,"labels":2917,"number":2919,"owner":2869,"repository":2870,"state":2883,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Is your feature request related to a problem? Please describe.\r\n\r\nI’m trying to customize a blog theme to display a 'tags' page\r\n\r\n### Describe the solution you'd like\r\n\r\nhoping the route can be shown as something like 'https://a.com/tags/', and I want to achieve this in VitePress without needing to create a markdown file.\r\n\r\n### Describe alternatives you've considered\r\n\r\n\r\nI once considered using onBeforePageLoad to modify data in the router, such as title, frontmatter, component, and isNotFound, but I thought it might not be the best solution.\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.",[2918],{"name":2866,"color":2867},4080,"Questions about routing hops in custom topics","2025-05-05T10:54:52Z","https://github.com/vuejs/vitepress/issues/4080",0.74540496,{"description":2925,"labels":2926,"number":2927,"owner":2869,"repository":2870,"state":2883,"title":2928,"updated_at":2929,"url":2930,"score":2931},"**Is your feature request related to a problem? Please describe.**\r\nFor custom themes such as blogs, it is useful to have access to the directory structure and frontmatter data for nested pages. For example, if I have the following directory structure:\r\n```\r\n/blog/index.md\r\n/blog/post_1.md\r\n/blog/post_2.md\r\n```\r\nThen I would like to be able to create a clickable list of posts on the `/blog/index` page with information for nested posts such as the post title, date, etc.\r\n\r\nTo do this, I need to be able to retrieve the frontmatter data from `post_1` and `post_2` (titles, dates) as well as information about what nested pages (i.e. links) are available. \r\n\r\nAt the moment I see no way to see frontmatter or site structure information other than for the currently selected page?\r\n\r\nI realise that the current goal is to keep `vitepress` simple and lightweight, however, this change would make `vitepress` viable for themes such as blogs without IMHO complicating the conceptual purity of the package.\r\n\r\n**Describe the solution you'd like**\r\n- A site-level property in `siteData` containing information about the nested page structure (for building links).\r\n- A site-level property in `siteData` containing frontmatter data for each page.\r\n\r\n**Describe alternatives you've considered**\r\nI've looked around `siteData` and other locations, but don't currently see a way to recover this information. (Please let me know if there is a way!!)\r\n",[],111,"Please add support for nested page frontmatter data and link data","2023-01-21T14:35:33Z","https://github.com/vuejs/vitepress/issues/111",0.75087994,{"description":2933,"labels":2934,"number":2936,"owner":2869,"repository":2870,"state":2883,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the bug\n\nafter migrate package.json\r\n```json\r\n\"directories\": {\r\n \"doc\": \"records\"\r\n },\r\n```\r\nsitemap generate with sitemap.hostname but not add /records after host name\n\n### Reproduction\n\nsitemap.xml\n\n### Expected behavior\n\nloc shoud be http://test.com/records/ok.html not http://test.com/ok.html\n\n### System Info\n\n```Text\n\"vitepress\": \"^1.1.0\"\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.",[2935],{"name":2900,"color":2901},3799,"Vitepress dose not generate sitemap with directories:doc","2024-05-05T04:41:50Z","https://github.com/vuejs/vitepress/issues/3799",0.7510466,{"description":2942,"labels":2943,"number":2947,"owner":2869,"repository":2870,"state":2883,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\r\n\r\nWhen using [`base`](https://vitepress.vuejs.org/config/basics.html#base), `route.path` is different across client and server.\r\n\r\nFor example, when using base `/base/` and logging `route.path`, `vitepress build` will log `/index.html`, but when visited in the browser, it logs `/base/index.html`.\r\n\r\n\r\n### Reproduction\r\n\r\n[Minimal reproduction link](https://github.com/privatenumber/issue-reproductions/tree/master/reproductions/vuejs/vitepress/587)\r\n\r\n1. Create a project with the following files:\r\n\r\n.vitepress/config.js\r\n```js\r\nimport { defineConfig } from 'vitepress'\r\n\r\nexport default defineConfig({\r\n\tbase: '/base/'\r\n})\r\n```\r\n\r\nindex.md:\r\n```html\r\n\u003Cscript setup>\r\nimport { useRoute } from 'vitepress';\r\n\r\nconst route = useRoute();\r\nconsole.log(`\\n\\nBUG: \"route.path\" is different across server and client: \"${route.path}\"\\n\\n`);\r\n\u003C/script>\r\n\r\nHello world\r\n```\r\n\r\n2. Run`vitepress build` and see `/index.html` get logged\r\n\r\n3. Run `vitepress serve` and see `/base/index.html` get logged\r\n\r\n\r\n### Expected behavior\r\n\r\nFor `route.path` to be consistent across server and client.\r\n\r\n### System Info\r\n\r\n```shell\r\nN/A\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nRelated: https://github.com/vuejs/vitepress/issues/446\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.",[2944],{"name":2945,"color":2946},"duplicate","cfd3d7",587,"base not used in route.path in server side","2023-01-21T16:04:13Z","https://github.com/vuejs/vitepress/issues/587",0.7515725,{"description":2953,"labels":2954,"number":2955,"owner":2869,"repository":2870,"state":2883,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Describe the bug\r\n\r\nAfter upgrading the vitepress version to `0.17.0`, The following error is prompted:\r\n**TypeError: Cannot destructure property 'locales' of 'siteData.themeConfig' as it is undefined**\r\n\r\n### Reproduction\r\n\r\n1. Change the version of `vitepress` in the `package.json` file from \"^0.16.1\" to \"^0.17.0\",\r\n2. run `yarn install`\r\n3. then run `yarn run docs:dev`\r\n4. which prompts the following error:\r\n```bash\r\nDebugger attached.\r\nyarn run v1.22.11\r\n$ vitepress dev docs\r\nDebugger attached.\r\nvitepress v0.17.0\r\nvite v2.5.2\r\nfailed to start server. error:\r\n TypeError: Cannot destructure property 'locales' of 'siteData.themeConfig' as it is undefined.\r\n at Object.createLangDictionary (C:\\Users\\yangquan6\\Documents\\yangquan666.github.io\\node_modules\\vitepress\\dist\\node\\shared.js:27:13)\r\n at resolveSiteData (C:\\Users\\yangquan6\\Documents\\yangquan666.github.io\\node_modules\\vitepress\\dist\\node\\config.js:80:25)\r\n at Object.resolveConfig (C:\\Users\\yangquan6\\Documents\\yangquan666.github.io\\node_modules\\vitepress\\dist\\node\\config.js:25:24)\r\n at async Object.createServer (C:\\Users\\yangquan6\\Documents\\yangquan666.github.io\\node_modules\\vitepress\\dist\\node\\server.js:8:20)\r\nWaiting for the debugger to disconnect...\r\nerror Command failed with exit code 1.\r\ninfo Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.\r\nWaiting for the debugger to disconnect...\r\n```\r\n\r\n### Expected behavior\r\n\r\nThe project starts normally and does not report errors\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.19042\r\n CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz\r\n Memory: 8.29 GB / 15.87 GB\r\n Binaries:\r\n Node: 14.17.6 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.11 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 6.14.15 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1023.0), Chromium (92.0.902.84)\r\n Internet Explorer: 11.0.19041.1\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/coc)\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.",[],379," Cannot destructure property 'locales' of 'siteData.themeConfig' as it is undefined.","2023-01-21T16:22:07Z","https://github.com/vuejs/vitepress/issues/379",0.75505835,["Reactive",2961],{},["Set"],["ShallowReactive",2964],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNv9FFxtGugOXlAYt8f7lungLgzHAzzETO0TA_BoDYwM":-1},"/vuejs/vitepress/159"]