`)\r\n\r\nI'm currently working on migrating and documenting the excellent Spectre CSS docs and am using Vitepress.\r\n\r\nI'm developing an ejected and modified default theme which has already come some way to solving this problem:\r\n\r\n- [original](https://picturepan2.github.io/spectre/components/menu.html) (custom app)\r\n- [migrated](https://spectre-org.github.io/spectre-docs/docs/components/menu.html) (VitePress with modified default theme)\r\n - note the `vp-doc` formatting which is all Spectre CSS\r\n - some fixed, and some not-yet fixed clashes of general class names\r\n\r\nFor reference to the use case (documenting a 3rd-party framework) here is the raw markdown page:\r\n\r\n- https://raw.githubusercontent.com/spectre-org/spectre-docs/main/docs/components/menu.md\r\n\r\nNote that:\r\n\r\n- Spectre CSS (or any other 3rd-party CSS framework) is now able to be simply \"dropped in\"\r\n- there is no pollution between VitePress and the 3rd-party framework\r\n- VitePress' default components remain fully-styled and work as they were before\r\n- `vp-doc` content can be safely used to demo any 3rd party HTML elements and classes\r\n\r\nI think I know enough to fix the problems in my modified theme and either:\r\n\r\n- publish a new \"neutral\" theme\r\n- port the changes to the default theme (ideal outcome)\r\n\r\nThere's actually not that much work; it's:\r\n\r\n- renaming the general component classes\r\n- moving some `vp-doc` classes to other locations\r\n- creating an additional unstyled entrypoint such as `without-formatting`\r\n\r\n### Describe alternatives you've considered\r\n\r\nPublishing the modified theme standalone, but then of course it would not benefit from ongoing updates.\r\n\r\n### Additional context\r\n\r\nI am proposing a PR in the coming weeks to integrate these updates.\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.",[2867],{"name":2868,"color":2869},"stale","ededed",3021,"vuejs","vitepress","open","Make the default theme compatible with 3rd-party CSS frameworks","2023-11-06T14:43:58Z","https://github.com/vuejs/vitepress/issues/3021",0.69336885,{"description":2879,"labels":2880,"number":2882,"owner":2871,"repository":2872,"state":2873,"title":2883,"updated_at":2884,"url":2885,"score":2886},"### Is your feature request related to a problem? Please describe.\r\n\r\nI want to use UnoCSS in a VitePress project, just like what [unocss.dev](https://unocss.dev) does. However, simply copying their config cannot bring UnoCSS to the whole site.\r\n\r\nIn this [minimal demo on StackBlitz](https://stackblitz.com/edit/vitepress-unocss), there are 3 UnoCSS injections:\r\n- [x] In Markdown content, any UnoCSS element keeps their format but without style\r\n- [ ] In the hero of `index.md`, the element turns into a string\r\n- [x] Only in the feature cards, element and styles exists so the icon shows\r\n- [ ] Other cases haven't been checked\r\n\r\n### Describe the solution you'd like\r\n\r\nProvide some guide to allow UnoCSS injection, it may be better if there is a plugin to do that.\r\n\r\n### Describe alternatives you've considered\r\n\r\nBoth VitePress and UnoCSS are powered by Vite, if UnoCSS can be integrated into VitePress, it may bring a more customizable style with little cost.\r\n\r\n~~I don't know if it's better to request this feature after UnoCSS reaches v1.0, or request it on UnoCSS for now.~~\r\n\r\n### Additional context\r\n\r\n- [UnoCSS docs source](https://github.com/unocss/unocss/tree/main/docs)\r\n- [Guide of integrating UnoCSS into Vite](https://unocss.dev/integrations/vite)\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.",[2881],{"name":2868,"color":2869},2424,"Feature request: support UnoCSS generally","2023-08-03T10:15:33Z","https://github.com/vuejs/vitepress/issues/2424",0.71427035,{"description":2888,"labels":2889,"number":2890,"owner":2871,"repository":2872,"state":2891,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### Describe the bug\r\n\r\nwhen I only bump vitepress from `v1.0.0-beta.3` to `v1.0.0-beta.5`, I find that the packing products appear \"Inter fonts\" files.\r\n\r\nI guess that is due to the new feature: `useSidebar`\r\n\r\ne.g. in v1.0.0-beta.5 `./client/theme-default/Layout.vue`, we will found:\r\n``` ts\r\nimport { useSidebar } from 'vitepress/theme'\r\n```\r\nmaybe we should replace to:\r\n```ts\r\nimport { useSidebar } from 'vitepress/theme-without-fonts'\r\n```\r\n\r\n\r\n### Reproduction\r\n\r\nsee `Describe the bug`\r\n\r\n### Expected behavior\r\n\r\nUsing I using Different Fonts, I don't need to generate the default inter font\r\n\r\n``` js\r\n// .vitepress/theme/index.js\r\nimport DefaultTheme from 'vitepress/theme-without-fonts'\r\nimport './my-fonts.css'\r\n\r\nexport default DefaultTheme\r\n```\r\n\r\n### System Info\r\n\r\n```sh\r\nvitepress: v1.0.0-beta.5\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] 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.",[],2587,"closed","[v1.0.0-beta5]: \"Inter fonts\" always appear in packaged products","2023-07-13T00:04:45Z","https://github.com/vuejs/vitepress/issues/2587",0.61333215,{"description":2897,"labels":2898,"number":2899,"owner":2871,"repository":2872,"state":2891,"title":2900,"updated_at":2901,"url":2902,"score":2903},"Hi there,\r\n\r\nThe example in the documentation for customizing the theme does not work. It fails as the file/package cannot be found. This is the [specific line](https://github.com/vuejs/vitepress/blob/ea6cb00c3e9099d45fc236bff0f7c42a65d558dc/docs/guide/theming.md?plain=1#L97) that I am referring to, but I believe that the other lines that use this same thing will also fail.\r\n\r\nThe specific import that fails\r\n```javascript\r\nimport DefaultTheme from 'vitepress/theme'\r\n```\r\n\r\nI found an alternative import that works by looking into the downloaded node_module folder directly\r\n```javascript\r\nimport DefaultTheme from \"vitepress/dist/client/theme-default\";\r\n```\r\n\r\nIm not sure if this is the intended use or? If this is an actual issue, I can help with making a PR to update the docs, else if it is something that needs to be fixed with the deployment process so that the `DefaultTheme` can be exported from vitepress/theme then it would probably need help from someone else familiar with the process.\r\n\r\nThanks alot for your time!",[],442,"Example provided in theme documentation does not work","2023-01-21T16:20:15Z","https://github.com/vuejs/vitepress/issues/442",0.6625931,{"description":2905,"labels":2906,"number":2907,"owner":2871,"repository":2872,"state":2891,"title":2908,"updated_at":2909,"url":2910,"score":2911},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nWhen using a custom theme, importing composables like `useRoute` from `\"vitepress\"` in the Layout component also imports the styles for the default theme.\r\n\r\n**To Reproduce**\r\n\r\n1. Follow the [Getting Started guide](https://vitepress.vuejs.org/guide/getting-started.html) to create a new site\r\n2. Create `docs/.vitepress/theme/Layout.vue` with the following contents:\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CContent />\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n// import { useRoute } from \"vitepress\";\r\n// const route = useRoute();\r\n\u003C/script>\r\n```\r\n\r\n3. Create `docs/.vitepress/theme/index.js` with the following contents:\r\n\r\n```js\r\nimport Layout from \"./Layout.vue\";\r\n\r\nexport default {\r\n Layout,\r\n};\r\n```\r\n\r\n4. Run `yarn docs:dev` and open http://localhost:3000. Note the heading doesn't have any styles applied to it:\r\n\r\n\r\n\r\n5. Uncomment the lines in the `\u003Cscript setup>` section in `docs/.vitepress/theme/Layout.vue`. Note the heading now has the default styles applied to it, even though we only imported `useRoute`:\r\n\r\n\r\n\r\n**Expected behavior**\r\nThe heading should remain unstyled since we aren't explicitly importing any styles.\r\n\r\n**System Info**\r\n- vitepress version: v0.9.2\r\n- vite version: v1.0.0-rc.13\r\n- Node version: v12.20.0\r\n- OS version: macOS Catalina 10.15.7\r\n\r\n**Additional context**\r\nI had a quick look at the Vitepress code and it looks like the problem might be to do with this line: https://github.com/vuejs/vitepress/blob/309aa7a8d0e7ab08c1c9db258c74709a66b295cb/src/client/app/exports.ts#L29\r\n\r\nAdding the following to `docs/.vitepress/config.js`:\r\n\r\n```javascript\r\nmodule.exports = {\r\n alias: {\r\n \"/@default-theme/index\": \"/@theme/empty.js\",\r\n },\r\n};\r\n```\r\n\r\n...and creating an empty file `docs/.vitepress/theme/empty.js` prevents the default styles being applied.\r\n",[],182,"Importing default composables also imports default theme's styles","2023-01-21T16:23:59Z","https://github.com/vuejs/vitepress/issues/182",0.674565,{"description":2913,"labels":2914,"number":2918,"owner":2871,"repository":2872,"state":2891,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Describe the bug\r\n\r\nI wrote a custom VitePress theme with UnoCSS, and I tried to import the theme from another project.\r\n\r\nBut after imported, the dev server failed to render the page and reported \r\n\r\n```\r\n[plugin:vite:import-analysis] Failed to resolve import \"virtual:uno.css\" from \"../theme/.vitepress/theme/index.js\". Does the file exist?\r\n/home/projects/stackblitz-starters-9izmbf/theme/.vitepress/theme/index.js:3:9\r\n1 | // https://vitepress.dev/guide/custom-theme\r\n2 | import Layout from './Layout.vue';\r\n3 | import 'virtual:uno.css';\r\n | ^\r\n4 | \r\n5 | export default {\r\n```\r\n\r\nI'm not sure which part of it is wrong. I don't even know if this is a VitePress bug. Please check the Stackblitz repro below.\r\n\r\n### Reproduction\r\n\r\nThis StackBlitz project reproduces the bug. BTW, the start script might execute very slowly.\r\n\r\nhttps://stackblitz.com/edit/stackblitz-starters-9izmbf?file=readme.md\r\n\r\n### Expected behavior\r\n\r\nThe test project in the above StackBlitz repro with external theme to work normally without additional configuration.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 16.20.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.2 - /usr/local/bin/npm\r\n pnpm: 8.6.10 - /usr/local/bin/pnpm\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] 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.",[2915],{"name":2916,"color":2917},"bug: pending triage","e99695",2845,"Cannot use external theme with UnoCSS","2023-09-01T00:04:32Z","https://github.com/vuejs/vitepress/issues/2845",0.6748987,{"description":2924,"labels":2925,"number":2930,"owner":2871,"repository":2872,"state":2891,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Describe the bug\r\n\r\nWhen developing the custom theme, I introduced the icon style in the .vitepress/theme/index file and the default font was 16px. Since it was a global style after introduction, I used this icon in a page, so I changed the font with another style, set it to 24px, normal 24px for development display, overlaid 16px, but after packaging and deploying it to production, the overlaid was still 16px.\r\n\r\n### Reproduction\r\n\r\nInitially I was developing with 1.0.0-alpha.19, but later upgrading to 1.0.0-alpha.63 caused a production style exception, so I opened the packaged file and found a difference between the style file and 1.0.0-alpha.19. The order is different. The global styles introduced in the theme/index file are at the very end of the file, so the custom theme page styles are overridden.\r\n\r\n### Expected behavior\r\n\r\nThe style of the custom theme page should take precedence over the global style introduced in the theme/index file.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\r\n Memory: 7.32 GB / 15.80 GB\r\n Binaries:\r\n Node: 16.15.0 - D:\\node\\node.EXE\r\n Yarn: 1.22.19 - D:\\node\\yarn.CMD\r\n npm: 8.1.0 - D:\\node\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (111.0.1661.54)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.63 => 1.0.0-alpha.63\r\n```\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2926,2929],{"name":2927,"color":2928},"build","377ba8",{"name":2868,"color":2869},2150,"In custom theme development, styles load order is different for development and production","2024-01-11T00:04:48Z","https://github.com/vuejs/vitepress/issues/2150",0.6819418,{"description":2936,"labels":2937,"number":2944,"owner":2871,"repository":2872,"state":2891,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Is your feature request related to a problem? Please describe.\n\nIt would be nice to have the latest version of Inter for VitePress\n\n### Describe the solution you'd like\n\nI'd love if the `woff` files of the font would be update it to the latest version (4). The last change to those files were 2 years ago, way before version 4.\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.",[2938,2941],{"name":2939,"color":2940},"theme","0754FB",{"name":2942,"color":2943},"contribution welcome","11E4B8",3693,"Update Inter font family to version 4","2024-04-28T12:25:11Z","https://github.com/vuejs/vitepress/issues/3693",0.693507,{"description":2950,"labels":2951,"number":2953,"owner":2871,"repository":2872,"state":2891,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Describe the bug\r\n\r\nWhen following the documentation for extending the default theme; importing the theme and exported the extended theme results in the error `TS2708: Cannot use namespace 'DefaultTheme' as a value.`.\r\n\r\n\r\n### Reproduction\r\n\r\nIn a bare VitePress installation:\r\n\r\n`docs/.vitepress/theme/index.ts`\r\n```ts\r\nimport { DefaultTheme } from \"vitepress/theme\";\r\n\r\nexport default {\r\n extends: DefaultTheme\r\n}\r\n```\r\n\r\n`docs/.vitepress/theme/index.ts:4:11: TS2708: Cannot use namespace 'DefaultTheme' as a value.`\r\n\r\n### Expected behavior\r\n\r\nThe documented code would work.\r\n\r\n### System Info\r\n\r\n```sh\r\n System:\r\n OS: Linux 6.1 Manjaro Linux\r\n CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor\r\n Memory: 17.45 GB / 31.30 GB\r\n Container: Yes\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 16.20.0 - ~/.local/bin/node\r\n Yarn: 1.22.19 - ~/.local/bin/yarn\r\n npm: 9.6.5 - ~/.local/bin/npm\r\n Browsers:\r\n Chromium: 114.0.5735.133\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.3 => 1.0.0-beta.3 \r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\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.",[2952],{"name":2916,"color":2917},2532,"Cannot create theme with TypeScript: TS2708: Cannot use namespace 'DefaultTheme' as a value.","2023-06-28T00:04:53Z","https://github.com/vuejs/vitepress/issues/2532",0.69370586,{"description":2959,"labels":2960,"number":2962,"owner":2871,"repository":2872,"state":2891,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Describe the bug\n\nCheck VP types here https://arethetypeswrong.github.io/?p=vitepress%401.0.0-beta.1, `vitepress/theme-without-fonts` types for node missing.\r\n\n\n### Reproduction\n\nhttps://arethetypeswrong.github.io/?p=vitepress%401.0.0-beta.1\n\n### Expected behavior\n\nTypes should be there\n\n### System Info\n\n```sh\nNA\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.",[2961],{"name":2916,"color":2917},2415,"missing vitepress/theme-without-fonts types for node","2023-06-02T00:04:15Z","https://github.com/vuejs/vitepress/issues/2415",0.6960493,["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhCDVrApa_s4r-ZOubYuspnu9XDM7KQOzdwE6p0vwNVE":-1},"/vuejs/vitepress/3411"]