\r\n\r\n::: zh-CN\r\n中文\r\n:::\r\n\r\n::: en\r\nEnglish\r\n:::\r\n```\r\n\r\nThis reduces maintenance costs.\r\n\r\nI came up with a very low cost implementation - [CSS-I18N](https://github.com/valaxyjs/css-i18n)\r\nAnd I implemented it in my own project [valaxy](https://github.com/YunYouJun/valaxy).\r\n\r\nIt works well. You can preview it [here](https://valaxy.site/guide/i18n).\r\nAnd this is my implementation: [How to realize CSS i18n?](https://valaxy.site/posts/i18n#css-i18n-another-solution)\r\n\r\n---\r\n\r\nIt is very cost-effective and I hope to integrate it with vitepress.\r\nIf you agree with my proposal, please let me know and I can create a PR for vitepress.\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\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.",[2886],{"name":2860,"color":2861},3047,"CSS i18n in one page","2025-03-02T18:10:37Z","https://github.com/vuejs/vitepress/issues/3047",0.7125543,{"description":2893,"labels":2894,"number":2899,"owner":2863,"repository":2864,"state":2865,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Is your feature request related to a problem? Please describe.\n\nCurrently, the search results only display the page title and anchors (if any) in which the results appear in. I have many similar page titles for different contexts, which are organized as different sidebar directories. Without being able to see which sidebar directory a page is in, it can get confusing as to which page I am looking at.\n\n### Describe the solution you'd like\n\nIt will be nice to be able to see which sidebar sub-directory the pages are in, as is the case for Vuepress's built-in search option. Would it be possible to add an option to configure what fields to display in the search bar results in themeConfig?\r\n\r\n\n\n### Describe alternatives you've considered\n\nI have looked at the existing search options, but none seem to offer this functionality.\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.",[2895,2898],{"name":2896,"color":2897},"theme","0754FB",{"name":2860,"color":2861},3192,"Display directory heading in search results","2025-03-02T18:10:21Z","https://github.com/vuejs/vitepress/issues/3192",0.71493053,{"description":2905,"labels":2906,"number":2912,"owner":2863,"repository":2864,"state":2865,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Describe the bug\n\n\r\n\r\nOpen the image in a new page and zoom in, you will see the transparency causes the overlaying lines of the letters to be visible and this makes things to look ugly.on\n\n### Reproduction\n\n1. You can use this font to test things out: https://fonts.google.com/specimen/Vazirmatn\r\n2. Change the font-family to this ^^^ font.\r\n3. Change to dark mode.\r\n4. Use this text: `اعتبارسنجی اسکیما تایپاسکریپت-اول`\r\n5. Zoom and you can see it too.\n\n### Expected behavior\n\nSo the overlaying paths/lines are not visible.\n\n### System Info\n\n```Text\n.\n```\n\n\n### Additional context\n\nI think this doesn't happen with all Farsi/Persian fonts, but it's something that happens very often.\r\n\r\nThe only solution is to not use opacity with text content.\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.",[2907,2908,2911],{"name":2896,"color":2897},{"name":2909,"color":2910},"a11y","fbca04",{"name":2860,"color":2861},3313,"Consider not using opacity for any text content","2024-05-23T19:48:59Z","https://github.com/vuejs/vitepress/issues/3313",0.7175562,{"description":2918,"labels":2919,"number":2923,"owner":2863,"repository":2864,"state":2865,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### 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.",[2920,2921,2922],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2876,"color":2877},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.71872574,{"description":2929,"labels":2930,"number":2934,"owner":2863,"repository":2864,"state":2935,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### 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.",[2931],{"name":2932,"color":2933},"need more info","bdbefc",4158,"closed","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.6896178,{"description":2941,"labels":2942,"number":2943,"owner":2863,"repository":2864,"state":2935,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Is your feature request related to a problem? Please describe.\n\nnow the right side only shows the second level title of the blog. How can I change the level?\n\n### Describe the solution you'd like\n\nadd some guide about this function\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.",[],4421,"how can I have first level title or other level title shown on the right catalog?","2024-12-21T04:43:46Z","https://github.com/vuejs/vitepress/issues/4421",0.6901888,{"description":2949,"labels":2950,"number":2951,"owner":2863,"repository":2864,"state":2935,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Is your feature request related to a problem? Please describe.\n\nI want customisation\n\n### Describe the solution you'd like\n\nI want to edit the `#` that's inserted as text to the left of headers to the other symbol. Is it possible already? Couldn't find a way\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.",[],3587,"Change hashtag icon","2024-02-28T00:04:05Z","https://github.com/vuejs/vitepress/issues/3587",0.69034725,{"description":2957,"labels":2958,"number":2959,"owner":2863,"repository":2864,"state":2935,"title":2960,"updated_at":2961,"url":2962,"score":2963},"I noticed that `VitePress` imports `@vue/shared`, but it appears to only use one of its methods. However, there are more methods available in `@vue/shared`. Should `VitePress` directly import these additional methods from `@vue/shared` to reduce redundancy in the code?\r\n\r\nHere is one case of what I mentioned:\r\n\r\n`vitepress`:\r\nhttps://github.com/vuejs/vitepress/blob/a6a7645e942cc63c57ca5d79da4b76dee76d8a96/src/node/config.ts#L229\r\n\r\n`@vue/shared`:\r\nhttps://github.com/vuejs/core/blob/db374e54c9f5e07324728b85c74eca84e28dd352/packages/shared/src/general.ts#L52\r\n\r\nSeems that can directly use `import { isObject } from '@vue/shared`.",[],3720,"Reuse some of the existing methods in `@vue/shared`","2024-04-28T12:24:53Z","https://github.com/vuejs/vitepress/issues/3720",0.69934314,["Reactive",2965],{},["Set"],["ShallowReactive",2968],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuiG88hG3w57BoR3l_dYFOR6XNEma9wVwbXzjvieXE54":-1},"/vuejs/vitepress/4165"]