`)\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.",[3020],{"name":3021,"color":3022},"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.7152436,{"description":3032,"labels":3033,"number":3034,"owner":3024,"repository":3025,"state":3035,"title":3036,"updated_at":3037,"url":3038,"score":3039},"Hello!\r\n\r\nI'm using VitePress to build my personal knowledge base, but I've found some bugs in the process, some of which have already been found and fixed in issues. \r\n1. Doc footer text is invalid\r\n2. Footer text unable to use hyperlinks \r\n3. Some text buttons cannot switch languages\r\n4. The social link icon cannot be customized\r\n5. ...\r\n\r\nNow I would like to ask, when can the next version be updated? Thank you!",[],1003,"closed","When will the next version be available?","2022-07-21T06:11:41Z","https://github.com/vuejs/vitepress/issues/1003",0.68212044,{"description":3041,"labels":3042,"number":3046,"owner":3024,"repository":3025,"state":3035,"title":3047,"updated_at":3048,"url":3049,"score":3050},"\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\nA clear and concise description of what the bug is.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\n**System Info**\r\n- vitepress version:\r\n- vite version:\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[3043],{"name":3044,"color":3045},"bug: pending triage","e99695",307,"index.md 乱码如何解决? ","2023-01-21T16:22:22Z","https://github.com/vuejs/vitepress/issues/307",0.6875195,{"description":3052,"labels":3053,"number":3054,"owner":3024,"repository":3025,"state":3035,"title":3055,"updated_at":3056,"url":3057,"score":3058},"**Is your feature request related to a problem? Please describe.**\r\n\r\nCurrently a VuePress user and excited to move to VitePress (primarily because I've written my own VP themes from scratch, and this seems to be the main design goal for v3) but:\r\n\r\n- there are various key differences between the frameworks (bundler, plugins, config)\r\n- there are significant intentional omissions in v3 (rather large list in the docs)\r\n- it's still in development\r\n\r\nAs a new / migrating user, it's a bit of a minefield and difficult to know where to start when something is omitted.\r\n\r\n**Describe the solution you'd like**\r\n\r\nRather than clogging up the issues with questions, it would be cool to get an Awesome VitePress list going, so users could find alternative plugins, or dig through the code of known solutions (i.e. the Vue Blog) and see how it's been solved before.\r\n\r\n**Describe alternatives you've considered**\r\n\r\nClog up the issues with questions, bug @kiaking on Twitter, Google solutions, etc.\r\n\r\n**Additional context**\r\n\r\nHappy to help search and review resources to get it started.\r\n\r\n",[],253,"List of examples or some kind of Awesome VitePress repo","2023-01-28T15:54:22Z","https://github.com/vuejs/vitepress/issues/253",0.6925323,{"description":3060,"labels":3061,"number":1575,"owner":3024,"repository":3025,"state":3035,"title":3063,"updated_at":3064,"url":3065,"score":3066},"\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\nThe SideBar.js and NavBar.js components still reference `__DEV__` and should be replaced with `import.meta.env.DEV` to work with 0.4.0\r\n\r\n**To Reproduce**\r\nUse the default theme with 0.4.0\r\n\r\n**Expected behavior**\r\nNavBar and SideBar should not throw __DEV__ not defined errors\r\n\r\n**System Info**\r\n- vitepress version: 0.4.0\r\n- vite version: v1.0.0-beta.2\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[3062],{"name":3044,"color":3045},"Sidebar Navbar break on 0.4.0","2023-01-21T16:25:39Z","https://github.com/vuejs/vitepress/issues/28",0.69592226,{"description":3068,"labels":3069,"number":3071,"owner":3024,"repository":3025,"state":3035,"title":3072,"updated_at":3073,"url":3074,"score":3075},"\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\nAfter running npx vitepress, I open the browser and load the address of http://localhost:3000, but I get a error.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\nPS D:\\桌面\\demo> npx vitepress\r\nvitepress v0.5.0\r\nvite v1.0.0-rc.4\r\nlistening at http://localhost:3000\r\n[vite] Failed to resolve module import \"vue/dist/vue.runtime.esm-bundler.js.0.0-rc.5@vuedist\u000bue.runtime.esm-bundler.js\". (imported by /@app/components/Debug.vue)\r\n\r\n**Expected behavior**\r\nGetting \"Hello Vitepress\" in browser.\r\n\r\n**System Info**\r\n- vitepress version: v0.5.0\r\n- vite version: v1.0.0-rc.4\r\n- Node version: 12.14.0\r\n- OS version:10.0.19041 暂缺 Build 19041\r\n\r\n**Additional context**\r\n尤大大,I am you big fan.\r\n",[3070],{"name":3044,"color":3045},65,"服务启动之后,进入地址报错","2023-01-21T16:25:36Z","https://github.com/vuejs/vitepress/issues/65",0.6977861,{"description":3077,"labels":3078,"number":3085,"owner":3024,"repository":3025,"state":3035,"title":3086,"updated_at":3087,"url":3088,"score":3089},"We don't have this yet in `next-theme`, and we should.\r\n\r\nKeep in mind:\r\n\r\n- https://github.com/vuejs/vitepress/issues/668",[3079,3082],{"name":3080,"color":3081},"build","377ba8",{"name":3083,"color":3084},"theme","0754FB",669,"[next] add Last Updated feature","2023-01-21T14:35:45Z","https://github.com/vuejs/vitepress/issues/669",0.69865334,{"description":3091,"labels":3092,"number":3094,"owner":3024,"repository":3025,"state":3035,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Describe the bug\n\nPreviously, I matched my document website with the color scheme of the original theme. Now that the new theme has been changed to purple, the overall look has become very unattractive. \r\n\r\nI have two options now: \r\n1. Do not upgrade,\r\n2. Upgrade to fix other issues, but keep the color scheme unchanged.\n\n### Reproduction\n\nN/A\n\n### Expected behavior\n\nHow to keep the color scheme unchanged while upgrading to the latest version?\n\n### System Info\n\n```sh\nN/A\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.",[3093],{"name":3044,"color":3045},2783,"Configure the original theme color scheme","2023-08-21T00:04:11Z","https://github.com/vuejs/vitepress/issues/2783",0.7025948,{"description":3100,"labels":3101,"number":3104,"owner":3024,"repository":3025,"state":3035,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Describe the bug\n\n### dependencies\r\n\r\n`pnpm add @chenwei02/qy-element`\r\n> `@chenwei02/qy-element` has svg-icon component. svg files builded by vite-plugin-svg-icons.\r\n\r\n### docs\r\n`vitepress dev docs` is ok\r\n`vitepress build docs` then deploy to gh-pages, *.svg icon was blank.\r\n\r\n### Problem\r\nvitepress build docs . something is wrong.\r\n\r\n### Help\r\nI need help\n\n### Reproduction\n\npnpm add @chenwei02/qy-element\r\n\r\n*.md\r\n\u003Cqy-icon name=\"close\">\r\n\r\nvitepress build docs.\n\n### Expected behavior\n\nevery thing is ok.\n\n### System Info\n\n```sh\nvitepress : 1.0.0-alpha.64\r\n@chenwei02/qy-element: 1.0.2-p1\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.",[3102,3103],{"name":3044,"color":3045},{"name":3021,"color":3022},2385,"Vitepress build Problem","2023-08-18T00:04:08Z","https://github.com/vuejs/vitepress/issues/2385",0.7111814,{"description":3110,"labels":3111,"number":3112,"owner":3024,"repository":3025,"state":3035,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Is your feature request related to a problem? Please describe.\n\n功能类似 CF Pages 在 commit and push 后, Pages 会自动 build 并部署在对象存储或cdn上\n但是 EdgeOne Pages 可能只拷贝了 一次commit 丢失 git 的文件提交信息, 导致 所有页面的更新时间都变成 build 时间\n这似乎不能怪罪于 EdgeOne Pages 或 VitePress 任意一方, 所以想想问问 准对这个场景 有解决方案嘛\n\n### Describe the solution you'd like\n\n或许, 可以使用 pre-commit 独立一份生成更新时间的映射文件\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.",[],4818,"基于 EdgeOne Pages 自动构建的 VitePress 配置 lastUpdated 异常","2025-06-27T17:26:26Z","https://github.com/vuejs/vitepress/issues/4818",0.7123053,["Reactive",3118],{},["Set"],["ShallowReactive",3121],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$flFKtomgKtsoez6fQsNqZR8CaOYz5Q-r9QMWdD-3dsNg":-1},"/vuejs/vitepress/626"]