\r\n\u003CB />\r\n\r\n\u003Cscript setup>\r\n import A from './sections/a.md'\r\n import B from './sections/b.md'\r\n\u003C/script>\r\n```\r\n\r\n`a.md`:\r\n```\r\n## Title\r\n\r\ntest\r\n```\r\n\r\n`b.md`:\r\n```\r\n## Title2\r\n\r\ntest2\r\n```\r\n\r\n`[[toc]]` won't show anything because it doesn't parse the sub .md files\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior: Just use the code that I pasted\r\n\r\n**Expected behavior**\r\nI expect `[[toc]]` to take into account the markdown that is imported so that we can organise our text into different files\r\n\r\n**System Info**\r\n- vitepress version: latest\r\n- vite version: latest\r\n- Node version: latest\r\n- OS version: Mac OS M1 latest\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2908],{"name":2909,"color":2910},"need more info","bdbefc",266,"TOC won't parse imported markdown files","2023-01-21T14:35:41Z","https://github.com/vuejs/vitepress/issues/266",0.70412236,{"description":2917,"labels":2918,"number":2919,"owner":2869,"repository":2870,"state":2892,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Is your feature request related to a problem? Please describe.\n\nI have some `*.md` files under `docs/component/`, but I also need some `*.vue` files under `docs/component/`.\n\n### Describe the solution you'd like\n\nI want to move the dir like `component/`, `public/` to the `.vitepress/` dir? Is there any problem?\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.",[],1951,"Is possible to make docs/ only contains markdown file only?","2023-02-27T00:04:36Z","https://github.com/vuejs/vitepress/issues/1951",0.7083185,{"description":2925,"labels":2926,"number":2927,"owner":2869,"repository":2870,"state":2892,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Is your feature request related to a problem? Please describe.\n\nCurrently, Vitepress provides functions like `usePage` or `frontmatter` to retrieve frontmatter data of the rendered page. However, there is no built-in functionality to retrieve frontmatter data of multiple Markdown files within a directory.\r\n\r\nImagine I'm crafting a custom layout, possibly for a portfolio or blog page. Within my project directory, I have folders like `project/blog/` or `project/portfolio` alongside the main `index.md`. Inside these directories lie numerous Markdown files, each containing frontmatter data similar to this:\r\n\r\n```md\r\n---\r\ntitle: Blog Post Title\r\ndate: 2024-03-27\r\nauthor: John Doe\r\ntags: [blog, update]\r\nlayout: blog\r\n---\r\n\r\n# Blog Post Title\r\n\r\nThis is the content of your blog post, written in Markdown format.\r\n\r\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Sed eget turpis nec leo euismod fringilla vitae ut quam.\r\n```\r\n\r\nHowever, my challenge arises when attempting to access the frontmatter data of all these files. While Vitepress offers functions like usePage or frontmatter to retrieve individual page data, there isn't an equivalent function like usePages to access data from multiple files simultaneously.\n\n### Describe the solution you'd like\n\nI would like to propose the addition of a new function or hook, such as `usePages`, that allows developers to retrieve frontmatter data of all Markdown files within a specified directory. This would provide more flexibility and enable the creation of custom layouts for portfolio or blog-related pages.\n\n### Describe alternatives you've considered\n\nAs an alternative, developers currently have to manually parse Markdown files using Node.js scripts before building the Vitepress project. However, this approach is less convenient and may not integrate seamlessly with the Vitepress development workflow.\n\n### Additional context\n\nBy adding support for retrieving frontmatter data of multiple Markdown files, developers can streamline the development process and create more dynamic and customizable layouts for their Vitepress projects. This feature would enhance the flexibility and usability of Vitepress, making it even more appealing for building static websites and blogs.\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.",[],3710,"Feature Request: Add Support for Retrieving Frontmatter Data from Multiple Markdown Files","2024-04-28T12:25:23Z","https://github.com/vuejs/vitepress/issues/3710",0.71850294,{"description":2933,"labels":2934,"number":2936,"owner":2869,"repository":2870,"state":2892,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### 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.",[2935],{"name":2889,"color":2890},3409,"index.md","2024-01-13T00:04:51Z","https://github.com/vuejs/vitepress/issues/3409",0.72243714,{"description":2942,"labels":2943,"number":2945,"owner":2869,"repository":2870,"state":2892,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the bug\n\nmd file can't use import @vicons/antd\r\n\r\n**My Code**\r\n:::demo\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cwp-icon name=\"DeleteOutlined\">\u003C/wp-icon>\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\" setup>\r\nimport {RightOutlined} from '@vicons/antd';\r\n\u003C/script>\r\n```\r\n:::\r\n\r\n\r\n\r\n**Browser Error**\r\n\r\n\n\n### Reproduction\n\nmd file use import\n\n### Expected behavior\n\nmd file can use import node_modules package\n\n### System Info\n\n```shell\n\"vitepress\": \"1.0.0-alpha.4\"\r\n\"@vicons/antd\": \"^0.11.0\"\r\n\"vite\": \"^2.9.0\"\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.",[2944],{"name":2889,"color":2890},922,"md file can't use import external resources","2023-01-21T14:32:45Z","https://github.com/vuejs/vitepress/issues/922",0.7266093,{"description":2951,"labels":2952,"number":2954,"owner":2869,"repository":2870,"state":2892,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Vue version\n\n3.2.45\n\n### Link to minimal reproduction\n\nhttps://github.com/newstart0514/vueProblem\n\n### Steps to reproduce\n\nUse vitepress to set the file route normally. The file is routed to the md file (needs to be imported to the local). This error occurs when opening the route\n\n### What is expected?\n\nThe md file will be converted to html normally\n\n### What is actually happening?\n\nAn error occurred and rendering cannot be performed normally. The error message is: Unhandled error during execution of scheduler flush This is likely a Vue internals bug.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.22000\r\n CPU: (16) x64 AMD Ryzen 7 4800U with Radeon Graphics\r\n Memory: 4.01 GB / 15.37 GB\r\n Binaries:\r\n Node: 18.12.1 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.18 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.19.2 - D:\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22000.120.0), Chromium (110.0.1587.63)\r\n Internet Explorer: 11.0.22000.120\r\n npmPackages:\r\n vue: ^3.2.45 => 3.2.45\n```\n\n\n### Any additional comments?\n\n_No response_",[2953],{"name":2909,"color":2910},2046,"An error occurred when rendering a markdown file when using vitepress","2023-06-01T00:04:29Z","https://github.com/vuejs/vitepress/issues/2046",0.7293569,["Reactive",2960],{},["Set"],["ShallowReactive",2963],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fadAm55BSiIksTfxDDGZpd_oWUOL4QqYf7DlVOK2Es4M":-1},"/vuejs/vitepress/411"]