\n\n\u003Cimg width=\"376\" height=\"181\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2f33e227-2f78-4d2d-a90e-796eb5842643\" />\n\n### Reproduction\n\nUse the default tempalte \"no style\" and add a code block with line-numbers.\n\nTested version: \"vitepress\": \"^1.6.3\"\n\n### Expected behavior\n\nThe line numbers are next to the code.\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 10 10.0.19045\n CPU: (16) x64 AMD Ryzen 7 5800X3D 8-Core Processor\n Memory: 11.37 GB / 31.92 GB\n Binaries:\n Node: 22.3.0 - C:\\Program Files\\nodejs\\node.EXE\n Yarn: 1.22.17 - ~\\AppData\\Roaming\\npm\\yarn.CMD\n npm: 9.8.1 - C:\\Program Files\\nodejs\\npm.CMD\n Browsers:\n Chrome: 138.0.7204.169\n Edge: Chromium (136.0.3240.92)\n Internet Explorer: 11.0.19041.5794\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\nTested on Chrome, Edge and Firefox - all have the same issue.\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.",[3020],{"name":3021,"color":3022},"bug: pending triage","e99695",4865,"vuejs","vitepress","closed","markdown :line-numbers","2025-07-29T22:58:24Z","https://github.com/vuejs/vitepress/issues/4865",0.68266207,{"description":3032,"labels":3033,"number":3040,"owner":3024,"repository":3025,"state":3026,"title":3041,"updated_at":3042,"url":3043,"score":3044},"### Is your feature request related to a problem? Please describe.\n\nI am frustrated and find it difficult in implement LaTeX onto the vitepress\n\n### Describe the solution you'd like\n\nThere are many packages on applying LaTeX to the website, e.g. Mathjax\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/coc)\n- [X] Read the [docs](https://vitepress.vuejs.org/).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3034,3037],{"name":3035,"color":3036},"build","377ba8",{"name":3038,"color":3039},"has-workaround","1B4515",529,"KaTeX/MathJax implementation","2023-09-28T00:04:09Z","https://github.com/vuejs/vitepress/issues/529",0.69752765,{"description":3046,"labels":3047,"number":3049,"owner":3024,"repository":3025,"state":3026,"title":3050,"updated_at":3051,"url":3052,"score":3053},"\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\n\r\nWhen the page title is `21E08`. And after build, It will goes as `210000000`. It was treated as scientific notation number \r\n\r\n**To Reproduce** \r\n\r\nSet page frontmatter like next\r\n\r\n```yaml\r\n---\r\ntitle: 21E08\r\nsubtitle: \"xxxxx\"\r\ndate: 2021-03-05\r\ncategory: \"xxx\"\r\n---\r\n```\r\n\r\n**Expected behavior** \r\n\r\nExpect the title will be treated as string not the number\r\n\r\n**System Info** \r\n- vitepress v0.11.3\r\n- vite v2.0.0-beta.30\r\n- Node version: v15.4.0\r\n- OS version: Big Sur 11.0.1 (20B29)\r\n\r\n",[3048],{"name":3021,"color":3022},255,"Markdown Page Title Parse Error","2023-01-21T16:22:29Z","https://github.com/vuejs/vitepress/issues/255",0.7123332,{"description":3055,"labels":3056,"number":3060,"owner":3024,"repository":3025,"state":3026,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Describe the bug\n\nAccording to [the configuration option](https://vitepress.vuejs.org/config/app-configs.html#markdown) of the documentation, this option is enabled:\r\n\r\n```ts\r\n// .vitepress/config.ts\r\nexport default defineConfig({\r\n // ...\r\n markdown: {\r\n lineNumbers: true,\r\n },\r\n // ...\r\n})\r\n```\r\n\r\nNot getting the expected result showing line numbers , by the way, the code snippets of the documentation also have no line numbers:\r\n\r\n\r\n\r\n\n\n### Reproduction\n\n```ts\r\n// .vitepress/config.ts\r\nexport default defineConfig({\r\n // ...\r\n markdown: {\r\n lineNumbers: true,\r\n },\r\n // ...\r\n})\r\n```\n\n### Expected behavior\n\nShow the code line numbers.\r\n\r\n\r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (12) x64 Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz\r\n Memory: 8.46 GB / 15.91 GB\r\n Binaries:\r\n Node: 16.15.0 - D:\\Programs\\nodejs\\node.EXE\r\n Yarn: 1.22.18 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.11.0 - D:\\Programs\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.62)\r\n Internet Explorer: 11.0.19041.1202\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.4 => 1.0.0-alpha.4\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3057],{"name":3058,"color":3059},"need more info","bdbefc",1046,"markdown.lineNumbers doesn't work under default theme","2023-01-21T14:30:12Z","https://github.com/vuejs/vitepress/issues/1046",0.71347606,{"description":3066,"labels":3067,"number":3072,"owner":3024,"repository":3025,"state":3026,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### Describe the bug\r\n\r\nI have the markdown file name as: 02.2023_04_GB55030.md\r\n\r\nI have the config like this:\r\n```\r\n sidebar: {\r\n /////////////////////////////////////////////////////////////////////////////////////////\r\n '/Resource/': [\r\n {\r\n text: '新规提示', collapsed: false,\r\n items: [\r\n { text: '日常提醒', link: '/Resource/000.新规提示/00.日常提醒' },\r\n { text: '2023_03_GB55新规', link: '/Resource/000.新规提示/01.2023_03_GB55新规' },\r\n { text: '2023_04_GB55030', link: '/Resource/000.新规提示/02.2023_04_GB55030' },\r\n { text: '2023_06_GB55037', link: '/Resource/000.新规提示/03.2023_06_GB55037' },\r\n ],\r\n...\r\n\r\n```\r\nWorks fine in dev mode.\r\nHowever, the \"02.2023_04_GB55030\" link does not work in build mode. The link should end with `.html`, but it is missing and shows as 404.\r\n\r\nIf I change the code from\r\n```\r\n{ text: '2023_04_GB55030', link: '/Resource/000.新规提示/02.2023_04_GB55030' },\r\n```\r\nTo\r\n```\r\n{ text: '2023_04_GB55030新规', link: '/Resource/000.新规提示/02.2023_04_GB55030新规' },\r\n```\r\nand rename the file `02.2023_04_GB55030.md` to `02.2023_04_GB55030新规.md`\r\n\r\nThen the link will work fine, in both dev mode and build mode.\r\n\r\n\r\n### Reproduction\r\n\r\nas mentioned earlier\r\n\r\n### Expected behavior\r\n\r\nit should work in build mode.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz\r\n Memory: 48.30 GB / 63.73 GB\r\n Binaries:\r\n Node: 18.16.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 9.5.1 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Chromium (119.0.2151.97), ChromiumDev (121.0.2248.1)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.51 => 1.0.0-rc.31\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.",[3068,3069],{"name":3058,"color":3059},{"name":3070,"color":3071},"stale","ededed",3289,"Markdown filenames ending in numbers don't seem to link correctly","2024-01-09T00:05:12Z","https://github.com/vuejs/vitepress/issues/3289",0.716689,{"description":3078,"labels":3079,"number":3084,"owner":3024,"repository":3025,"state":3026,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Describe the bug\n\nWhen allowing word wrap in code blocks, the line numbers don't work correctly.\r\n\r\n\n\n### Reproduction\n\n1. set the code block to allow text wrap:\r\n\r\n```\r\n code {\r\n white-space: pre-wrap !important;\r\n }\r\n```\r\n\r\n2. set line numbers to true in config.ts\r\n```\r\nexport default defineConfig({\r\n markdown: { lineNumbers: true }\r\n})\r\n```\r\n\r\n4. write a long line of code, you can see something like the following:\r\n\r\n\u003Cimg width=\"726\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/3367820/12fbabb1-7adf-40a9-a740-d73b57aef4d1\">\r\n\n\n### Expected behavior\n\nThe line number should not increment until a new line met\n\n### System Info\n\n```sh\nSystem:\r\n OS: macOS 13.4.1\r\n CPU: (10) x64 Apple M1 Pro\r\n Memory: 32.79 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm\r\n Watchman: 2023.05.08.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Safari: 16.5.1\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.",[3080,3083],{"name":3081,"color":3082},"theme","0754FB",{"name":3038,"color":3039},2567,"Code line numbers don't work well with text wrap","2023-07-10T00:05:11Z","https://github.com/vuejs/vitepress/issues/2567",0.7228717,{"description":3090,"labels":3091,"number":3093,"owner":3024,"repository":3025,"state":3026,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Describe the bug\n\nin my markdown file i have\n\n```\n---\nhello: world\n---\n\n## Markdown Content\n\n\u003Cp v-for=\"a in [1, 23]\"\n :key=\"1\"\n >\n {{ a }}\n\u003C/p>\n\n```\nNormally a vuejs app shows a warning that the key is duplicate, but it does not happen in a vitepress app. \n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-4jdq3cfy?file=docs%2Fexample.md\n\n### Expected behavior\n\nin dev mode the warning should be shown\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 6.8 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\n Memory: 14.78 GB / 30.23 GB\n Container: Yes\n Shell: 5.2.21 - /bin/bash\n Binaries:\n Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node\n Yarn: 4.6.0 - ~/.yarn/bin/yarn\n npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm\n Browsers:\n Brave Browser: 133.1.75.178\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.",[3092],{"name":3058,"color":3059},4577,"vitepress does not show vue warnings","2025-03-13T04:44:38Z","https://github.com/vuejs/vitepress/issues/4577",0.72818476,{"description":3099,"labels":3100,"number":3102,"owner":3024,"repository":3025,"state":3026,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Describe the bug\n\nhttps://stackblitz.com/edit/vite-j7cesz?file=docs/index.md is the repro. Its `index.md` compiles just fine with some other established markdown compilers -- I tried pandoc and it worked well.\r\n\r\nI would like to know what's wrong with my markdown code! It can be that I don't understand the VitePress markdown syntax well enough, or maybe I am lucky to find a bug in the compiler 😉 I would like to provide additional info amap.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-j7cesz?file=docs/index.md\n\n### Expected behavior\n\nCompiles just fine.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)\r\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H\r\n Memory: 5.91 GB / 7.61 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 19.2.0 - /usr/bin/node\r\n npm: 8.19.3 - /usr/bin/npm\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.30 => 1.0.0-alpha.30\r\n```\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3101],{"name":3021,"color":3022},1673,"VitePress does not compile a HTML-markdown mixed file saying that 'Element is missing end tag'","2023-01-21T14:17:06Z","https://github.com/vuejs/vitepress/issues/1673",0.729481,{"description":3108,"labels":3109,"number":3111,"owner":3024,"repository":3025,"state":3026,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Describe the bug\n\nIf I insert a codepen demo into a markdown page, everything works as expected during development. But in prod (or in preview) all the content after a custom Vue element (that adds a script tag to the page) is duplicated. \n\n### Reproduction\n\nAll the changes that are needed to reproduce the bug in a new project are in this commit:\r\nhttps://github.com/deenns/vitepress-bugs/commit/687c84c424b7159271a82a856af3ddd24b3e9e63\r\n\r\n1. Clone the repo https://github.com/deenns/vitepress-bugs\r\n2. Run \r\n ```\r\n npm i\r\n npm run docs:build\r\n npm run docs:preview\r\n ```\r\n3. Open the `/markdown-examples.html` page. There is a codepen demo, and everything is ok.\r\n4. Click on the \"Runtime API Examples\" in the sidebar, and then click on the \"Markdown Examples\" to return back.\r\n5. Now all the content after the codepen demo is rendered twice. \r\n\r\nA workaround: \r\n\r\nIf you move the `\u003CScriptElement />` to the end of the markdown file, the problem will disappear. \n\n### Expected behavior\n\nIt must not duplicate the content after the script element. It works correctly in dev. \n\n### System Info\n\n```sh\n\"vitepress\": \"^1.0.0-beta.2\"\r\n```\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.",[3110],{"name":3038,"color":3039},2506,"Markdown after custom element with codepen script is duplicated in production","2023-06-25T00:05:07Z","https://github.com/vuejs/vitepress/issues/2506",0.73272383,{"description":3117,"labels":3118,"number":3119,"owner":3024,"repository":3025,"state":3026,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Describe the bug\n\nAfter upgrading to version 2.0.0-alpha7, pages in createContentLoader is rendered asynchronously, the docs seem to be wrong.\n\n### Reproduction\n\nTo minimize disruption, I pasted the example codes to my project, and the issue is still existing.\n\n```posts.data.js\nimport { createContentLoader } from 'vitepress'\n\nexport default createContentLoader('posts/*.md', {\n includeSrc: true, // include raw markdown source?\n render: true, // include rendered full page HTML?\n excerpt: true, // include excerpt?\n transform(rawData) {\n // map, sort, or filter the raw data as you wish.\n // the final result is what will be shipped to the client.\n return rawData.sort((a, b) => {\n return +new Date(b.frontmatter.date) - +new Date(a.frontmatter.date)\n }).map((page) => {\n page.src // raw markdown source\n page.html // rendered full page HTML\n page.excerpt // rendered excerpt HTML (content above first `---`)\n return {/* ... */}\n })\n }\n})\n```\n\n```posts.html\n\u003Cscript setup>\nimport { data as posts } from './posts.data.js'\n\u003C/script>\n\n\u003Cbody>\n \u003Ch1>All Blog Posts\u003C/h1>\n \u003Cul>\n \u003Cli v-for=\"post of posts\">\n \u003Ca :href=\"post.url\">{{ post.frontmatter.title }}\u003C/a>\n \u003Cspan>by {{ post.frontmatter.author }}\u003C/span>\n \u003C/li>\n \u003C/ul>\n\u003Cbody>\n```\n\n### Expected behavior\n\nThe post list should not be empty.\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (12) x64 13th Gen Intel(R) Core(TM) i7-13700K\n Memory: 4.18 GB / 11.98 GB \nBinaries:\n Node: 22.17.0 - C:\\Program Files\\nodejs\\node.EXE\n npm: 11.4.2 - C:\\Program Files\\nodejs\\npm.CMD\nBrowsers:\n Edge: Chromium (129.0.2792.65)\nnpmPackages:\n vitepress: ^2.0.0-alpha.7 => 2.0.0-alpha.7\n```\n\n### Additional context\n\nI have checked following steps:\n\n- Codes I copied are not modified except path.\n- The paths are correct.\n- The file list is not empty.\n\nIf you can not reproduct the issue, I can provide my project.\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.",[],4822,"docs issue in createContentLoader","2025-07-03T05:06:00Z","https://github.com/vuejs/vitepress/issues/4822",0.7349735,["Reactive",3125],{},["Set"],["ShallowReactive",3128],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fl2rE7sJ8sCrhed70pWfSOg4T5yD8rb2dJi80B7TAf-c":-1},"/vuejs/vitepress/4740"]