```\r\n\r\nIt doesn't seem to be correct:\r\n\r\n\r\n\r\nHow to make it look correct, just like on the homepage?:\r\n\r\n\r\n\r\n",[2893],{"name":2868,"color":2869},4273,"How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.73073536,{"description":2900,"labels":2901,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Describe the bug\r\n\r\nUsing `@babylonjs/loaders` will cause an error during the build phase: `KHR_animation_pointer.data.js`: config must export or return an object.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-v1c8np4w\r\n\r\nRun `npm run docs:build`.\r\n\r\n### Expected behavior\r\n\r\nThe error \"config must export or return an object\" should not occur.\r\n\r\nRemoving `import '@babylonjs/loaders'` will prevent any errors from occurring.\r\n\r\nI suspect it might be due to the filename `KHR_animation_pointer.data.js`, which might cause VitePress to mistakenly identify it as a `data loader`, leading to this error.\r\n\r\nIf my guess is correct, might there be a need for a way to exclude specific files?\r\n\r\n### System Info\r\n\r\n```Text\r\n@babylonjs/loaders: 7.43.0\r\nvitepress: 1.5.0\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n> vitepress build docs\r\n\r\n\r\n vitepress v1.5.0\r\n\r\n⠇ building client + server bundles...failed to load config from /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js\r\nx Build failed in 3.63s\r\n✖ building client + server bundles...\r\nbuild error:\r\n[commonjs--resolver] Could not load /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js: config must export or return an object.\r\n[commonjs--resolver] Could not load /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js: config must export or return an object.\r\n at Module.loadConfigFromFile (file:///home/projects/vite-v1c8np4w/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:66589:13)\r\n at async Object.load (file:///home/projects/vite-v1c8np4w/node_modules/vitepress/dist/node/chunk-DMuPggCS.js:44533:21)\r\n \r\n \r\n\r\n\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.",[2902,2905,2906],{"name":2903,"color":2904},"build","377ba8",{"name":2868,"color":2869},{"name":2907,"color":2908},"needs more discussion","C2E0C6",4482,"Using babylonjs/loaders, the error \"config must export or return an object\" occurs","2025-03-02T18:07:54Z","https://github.com/vuejs/vitepress/issues/4482",0.73118865,{"description":2915,"labels":2916,"number":2920,"owner":2871,"repository":2872,"state":2921,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Describe the bug\n\n```import { createContentLoader } from 'vitepress'\r\ninterface Post{\r\n title: string\r\n date: Date\r\n cover: string | undefined\r\n description: string | undefined\r\n tags: string[] | undefined\r\n categorie: string | undefined\r\n url:string\r\n author: string | undefined\r\n}\r\n\r\ndeclare const data: Post[]\r\nexport { data }\r\nexport default createContentLoader(['**/*.md','!**/index.md','!nav.md','!archives.md','!posts.md'], {\r\n includeSrc: false, \r\n render: false,\r\n excerpt: false,\r\n transform(raw): Post[] {\r\n console.log(\"row\",raw);\r\n return raw\r\n .map(({url, frontmatter }) => ({\r\n title: frontmatter.title,\r\n cover:frontmatter.cover,\r\n description:frontmatter.description,\r\n tags:frontmatter.tags,\r\n categorie:frontmatter.categorie,\r\n date: frontmatter.date,\r\n url: url,\r\n author: frontmatter.author\r\n }))\r\n }\r\n})\r\n```\r\nIn the above code, I utilize createContentLoader to retrieve information from all *.md files; however, I do not require data from index.md or nav.md files located in any directory. I have employed glob patterns for this purpose, but they seem not to be taking effect. How should I address this issue?\n\n### Reproduction\n\ndocs\r\n | ---index.md\r\n | ---foo.md\r\n | --- vue\r\n | --- index.md\r\n | --- foo2.md\n\n### Expected behavior\n\ndocs\r\n | ---foo.md\r\n | --- vue\r\n | --- foo2.md\n\n### System Info\n\n```Text\nvitepress-version: 1.0.2\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.",[2917],{"name":2918,"color":2919},"bug: pending triage","e99695",3821,"closed","Watch is not effectively utilizing glob patterns","2024-05-15T04:41:47Z","https://github.com/vuejs/vitepress/issues/3821",0.6775461,{"description":2927,"labels":2928,"number":2932,"owner":2871,"repository":2872,"state":2921,"title":2933,"updated_at":2934,"url":2935,"score":2936},"Hello VitePress Team,\r\n\r\nI am encountering two issues with my VitePress project and seeking guidance.\r\n\r\n1. **Sidebar Title Formatting Not Effective**: \r\n I have been trying to customize the sidebar title formatting in my VitePress site, but it seems not to be working as expected. Despite using the recommended plugins, including `toc`, the sidebar either doesn't reflect the specified title formats or disappears completely. Attached is a screenshot of my current interface for reference:\r\n \r\n\r\n Here is the code snippet I am using (I've ensured all necessary libraries are installed):\r\n \r\n\r\n Could you please clarify if there's anything I am missing or doing incorrectly? Any guidance on how to properly format the sidebar titles would be greatly appreciated.\r\n\r\n2. **Navigation Placement on the Left**:\r\n I am trying to achieve a layout similar to VuePress where the navigation is on the left side. Although I have disabled the sidebar and set `aside: \"left\"`, the final layout seems to have excessive white space on the left. How should I configure it to get the desired layout? Here is a screenshot showing the current layout:\r\n \r\n\r\nThank you for your assistance. Looking forward to your suggestions and solutions.\r\n",[2929],{"name":2930,"color":2931},"question","5D5FAE",3422,"侧边栏配置","2024-01-16T00:04:37Z","https://github.com/vuejs/vitepress/issues/3422",0.7082721,{"description":2938,"labels":2939,"number":2943,"owner":2871,"repository":2872,"state":2921,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Describe the bug\n\nbuild error:\r\nThe requested module 'vue' does not provide an export named 'default'\r\nfile:///Users/lee/Codes/Work/PanSoft/pan-ui-vue/apps/docs/.vitepress/.temp/index.gDrBdFYw.js:1\r\nimport require$$0, { defineComponent, createVNode, ref, computed, watch, Fragment, watchEffect, createTextVNode, toRaw, mergeModels, useModel, openBlock, createBlock, unref, mergeProps, createSlots, withCtx, normalizeClass, createElementBlock, createElementVNode, toDisplayString, renderList, renderSlot, normalizeProps, nextTick } from \"vue\";\r\n\r\nSyntaxError: The requested module 'vue' does not provide an export named 'default'\r\n at ModuleJob._instantiate (node:internal/modules/esm/module_job:132:21)\r\n at async ModuleJob.run (node:internal/modules/esm/module_job:214:5)\r\n at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)\r\n at async build (file:///Users/lee/Codes/Work/PanSoft/pan-ui-vue/node_modules/.pnpm/vitepress@1.3.3_@algolia+client-search@4.24.0_@types+node@22.0.0_async-validator@4.2.5_less@4_vyupewqor5ionkpvva6zm6cw7u/node_modules/vitepress/dist/node/serve-lJPQ9bCN.js:47053:24)\n\n### Reproduction\n\n{\r\n \"name\": \"docs\",\r\n \"private\": true,\r\n \"scripts\": {\r\n \"dev\": \"vitepress dev\",\r\n \"docs:build\": \"vitepress build\",\r\n \"docs:preview\": \"vitepress preview\"\r\n },\r\n \"dependencies\": {\r\n \"@panui-vue/base\": \"workspace:*\",\r\n \"@panui-vue/pro\": \"workspace:*\",\r\n \"@panui-vue/icon\": \"workspace:*\",\r\n \"@panui-vue/excel\": \"workspace:*\",\r\n \"vue\": \"^3.4.31\",\r\n \"lodash-es\": \"^4.17.21\",\r\n \"@formily/vue\": \"^2.3.2\",\r\n \"dayjs\": \"1.11.12\"\r\n },\r\n \"devDependencies\": {\r\n \"@faker-js/faker\": \"^8.4.1\",\r\n \"@vitepress-demo-preview/component\": \"^2.3.2\",\r\n \"@vitepress-demo-preview/plugin\": \"^1.2.3\",\r\n \"postcss\": \"^8.4.40\",\r\n \"rollup-plugin-visualizer\": \"^5.12.0\",\r\n \"typescript\": \"^5.2.2\",\r\n \"vitepress\": \"^1.3.3\",\r\n \"@types/lodash-es\": \"^4.17.12\",\r\n \"@vitejs/plugin-vue-jsx\": \"^4.0.0\"\r\n }\r\n}\n\n### Expected behavior\n\nNormal build\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.6.1\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 185.47 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node\r\n npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm\r\n pnpm: 9.7.1 - ~/.nvm/versions/node/v20.11.1/bin/pnpm\r\n Browsers:\r\n Chrome: 127.0.6533.120\r\n Edge: 127.0.2651.105\r\n Safari: 17.6\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.",[2940],{"name":2941,"color":2942},"need more info","bdbefc",4158,"SyntaxError: The requested module 'vue' does not provide an export named 'default'","2024-09-03T04:42:37Z","https://github.com/vuejs/vitepress/issues/4158",0.70830333,{"description":2949,"labels":2950,"number":2952,"owner":2871,"repository":2872,"state":2921,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Describe the bug\n\nI installed Vitepress, built then ran it locally following the documentation of Vercel and everything seemed fine. But when I deployed it to my personal Vercel, my site keeps loading the 404.html. When I visit the Output of Vercel, I couldn't find any index.html and only 404.html. \r\n\r\nHere is currently [the blog of mine](https://vitepress-doc-kappa.vercel.app/) that I deployed to Vercel.\r\n\r\nThis is my current source on Vercel:\r\n\r\n\r\nThis is my current output on Vercel:\r\n\r\n\r\n\n\n### Reproduction\n\nNot sure if this is the correct way to reproduce, but I'll list down the commands that I ran, from install command to deploy:\r\n\r\n```bash\r\nnpm add -D vitepress\r\nnpx vitepress init ./\r\nnpm run docs:build\r\nnpm run docs:preview\r\nvercel --prod\r\n```\n\n### Expected behavior\n\nPage should load index.html when visiting `/`.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19043\r\n CPU: (4) x64 Intel(R) Pentium(R) CPU G4560 @ 3.50GHz\r\n Memory: 2.27 GB / 7.96 GB\r\n Binaries:\r\n Node: 20.0.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.6.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.133)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.39 => 1.0.0-rc.39\n```\n\n\n### Additional context\n\nI use a fresh setup of Vitepress and deploy to a Vercel setting using Node v20.x (which as mentioned on Vercel that is still in Beta). However I did try Node v18.x on Vercel and the error is the same. \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.",[2951],{"name":2918,"color":2919},3460,"Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.71177876,{"description":2958,"labels":2959,"number":2964,"owner":2871,"repository":2872,"state":2921,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Is your feature request related to a problem? Please describe.\n\nWhen a page is not found (404 error), the navbar content doesn't dynamically adapt to the selected language/locale despite the i18n setup.\r\n\r\nSteps to Reproduce:\r\n1. Set up VitePress with multiple languages.\r\n2. Navigate to a non-existent page to trigger a 404 error.\r\n3. Observe that the navbar content remains in English and doesn’t adjust based on the selected language/locale.\n\n### Describe the solution you'd like\n\nIdeally, the navbar content should follow the i18n configuration and display the appropriate language-specific content when encountering a 404 error.\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n### Expected:\r\n\r\n\r\n### Actual:\r\n\r\n\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.",[2960,2963],{"name":2961,"color":2962},"theme","0754FB",{"name":2868,"color":2869},3350,"404 page navbar should follow language settings","2024-05-10T04:42:01Z","https://github.com/vuejs/vitepress/issues/3350",0.72272366,{"description":2970,"labels":2971,"number":2972,"owner":2871,"repository":2872,"state":2921,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Is your feature request related to a problem? Please describe.\n\nThere is currently no easy way to set the text direction of an entire website. While it is possible to add global CSS, that is [not the recommended approach](https://www.w3.org/International/tutorials/bidi-xhtml/index#browser).\n\n### Describe the solution you'd like\n\nIt would be useful to add a config to set `dir=\"ltr/rtl\"` of the `\u003Chtml>` element, so that docs written in [RTL scripts](https://www.w3.org/International/questions/qa-scripts) using VP can be better supported.\n\n### Describe alternatives you've considered\n\nUse the CSS [direction](https://www.w3.org/TR/css-writing-modes-4/#direction) property to customize the theme.\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.",[],902,"How to set the text direction?","2023-01-25T00:04:23Z","https://github.com/vuejs/vitepress/issues/902",0.7255909,["Reactive",2978],{},["Set"],["ShallowReactive",2981],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_GQb0RNveaqfVQyqbtuy_fIgcr-12BBRvAqzlc1AeK0":-1},"/vuejs/vitepress/1692"]