\n这是知乎网站的热搜榜\n\n\u003Cimg width=\"807\" height=\"942\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/092b0749-e7d2-4b00-bd5b-172b6725c892\" />\n\n### Reproduction\n\n希望能更新接口,获取最新热搜数据\n\n### Expected behavior\n\n希望能更新接口,获取最新热搜数据\n\n### System Info\n\n```Text\n1.6.20\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.",[3090],{"name":3055,"color":3056},4866,"知乎热搜榜不更新","2025-07-30T04:05:01Z","https://github.com/vuejs/vitepress/issues/4866",0.75900495,{"description":3097,"labels":3098,"number":3100,"owner":3033,"repository":3034,"state":3058,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Describe the bug\n\nImage wasn't inlined, see https://stackblitz.com/edit/vite-upxxuh?file=package.json,vite.config.ts:\r\n\r\n\u003Cimg width=\"1919\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/3367820/7ab7ef71-c29e-4a24-9f96-36d06441e7b9\">\r\n\n\n### Reproduction\n\nsee https://stackblitz.com/edit/vite-upxxuh?file=package.json,vite.config.ts:\r\n\r\n\u003Cimg width=\"1919\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/3367820/7ab7ef71-c29e-4a24-9f96-36d06441e7b9\">\n\n### Expected behavior\n\nthe image should be base64 inlined according to https://vitepress.dev/guide/asset-handling#referencing-static-assets\n\n### System Info\n\n```Text\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: 18.18.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.10.5 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: v1.0.0-beta.7 => 1.0.0-beta.7\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.",[3099],{"name":3055,"color":3056},3370,"assets Inline doesn't work?","2023-12-30T00:04:35Z","https://github.com/vuejs/vitepress/issues/3370",0.7606127,{"description":3106,"labels":3107,"number":3108,"owner":3033,"repository":3034,"state":3058,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Is your feature request related to a problem? Please describe.\n\nCurrently the default theme hardcodes a string comparison to determine if current page is home layout:\n\n```js\nclass = {\n 'is-home': frontmatter.layout === 'home'\n}\n```\n\nThere are many occurrences in the default theme where the above expression is used to control special treatments for home pages (e.g. hide sidebar, disable local nav, expand content width in CSS).\n\nIn my case, I need to create a custom Home layout in addition to the one provided by the default theme. However, it's almost impossible to make a custom layout page behave like the home layout because of these hardcoded conditions.\n\n### Describe the solution you'd like\n\nAccept an optional config `isHomeLayout` in front-matter. When left undefined, this entry should default to `frontmatter.layout === 'home'`.\n\nExample:\n\n```md\n---\nlayout: my-custom-layout\nisHomeLayout: true\n---\n\n# My home content\n\nLorem ipsum dolor sit amet ....\n```\n\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.",[],4671,"[default-theme] Allow custom layout used as home layout","2025-04-05T13:59:33Z","https://github.com/vuejs/vitepress/issues/4671",0.760825,{"description":3114,"labels":3115,"number":3119,"owner":3033,"repository":3034,"state":3058,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Describe the bug\n\nThe colored remove diff (`[!code --]`) in a codeblock does not work in XML code due to how it's parser processes comments in relation to `--`, as described here:\n\nhttps://www.w3.org/TR/REC-xml/#sec-comments\n\n> [Definition: Comments may appear anywhere in a document outside other [markup](https://www.w3.org/TR/REC-xml/#dt-markup); in addition, they may appear within the document type declaration at places allowed by the grammar. They are not part of the document's [character data](https://www.w3.org/TR/REC-xml/#dt-chardata); an XML processor MAY, but need not, make it possible for an application to retrieve the text of comments. [For compatibility](https://www.w3.org/TR/REC-xml/#dt-compat), the string \" -- \" (double-hyphen) MUST NOT occur within comments.] Parameter entity references MUST NOT be recognized within comments.\n\n### Reproduction\n\nAdd the following to a markdown document:\n\n\\```xml\n\\\u003CReference Include=\"Assembly-CSharp\" HintPath=\"...\\Assembly-CSharp.dll\" /> \\\u003C!-- [!code --] -->\n\\\u003CReference Include=\"Assembly-CSharp\" HintPath=\"...\\Assembly-CSharp.dll\" Publicize=\"true\" /> \\\u003C!-- [!code ++] -->\n\\```\n\n### Expected behavior\n\nThe colored remove diff should appear.\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 6.13 openSUSE Tumbleweed 20250128\n CPU: (8) x64 AMD Ryzen 7 9800X3D 8-Core Processor\n Memory: 22.05 GB / 30.47 GB\n Container: Yes\n Shell: 5.2.37 - /bin/bash\n Binaries:\n Node: 22.13.1 - /usr/bin/node\n npm: 10.9.2 - /usr/bin/npm\n pnpm: 10.0.0 - /usr/bin/pnpm\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\nThe main way to support this that I can think of is to add an acceptable syntax of `[!code \\-\\-]`, `[!code -\\-]`, or some other syntax for diff coloring.\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.",[3116],{"name":3117,"color":3118},"upstream","BF29ED",4555,"XML Codeblock Colored Diff does not parse.","2025-02-20T04:43:04Z","https://github.com/vuejs/vitepress/issues/4555",0.7624233,["Reactive",3125],{},["Set"],["ShallowReactive",3128],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fu482nUuM55SZD0Rq7rje6oY7dTl82gz0ECJzyC2RG8s":-1},"/vuejs/vitepress/4297"]