\u003C/div>`. If I would style said `div` with a `padding: 8px`, it is expected that by nesting it 3 levels deep, I would end up with 3 div html elements, each pushing its child `8px` in. \r\n\r\nThe result is basically:\r\n\r\n```html\r\n\u003Cdiv class=\"spacer\">\r\n \u003Cdiv class=\"spacer\">\r\n \u003Cdiv class=\"spacer\">\u003Cslot />\u003C/div>\r\n \u003C/div>\r\n\u003C/div>\r\n```\r\n\r\n> **notice** how on line 5, I get back the actual, non-compiled template.\r\n\r\n\n\n### Reproduction\n\n- create a custom component, say a \u003CTest> component with a `\u003Cslot />`\r\n- import it to vitepress\r\n- write a `md` story and nest the component three times:\r\n\r\n```md\r\n\u003Ctest>\r\n \u003Ctest>\u003C/test>\r\n \u003Ctest>\r\n \u003Ctest>I get rendered as text, even if I contain an HTML element, such as a `\u003Cbutton>`\u003C/test>\r\n \u003C/test>\r\n\u003C/test>\r\n```\n\n### Expected behavior\n\ntemplate compiler should keep going through deeper levels of components and render them as HTML elements.\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.2\r\n CPU: (8) arm64 Apple M1\r\n Memory: 119.95 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node\r\n Yarn: 1.22.17 - /opt/homebrew/bin/yarn\r\n npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm\r\n Browsers:\r\n Chrome: 97.0.4692.99\r\n Safari: 15.3\r\n npmPackages:\r\n vitepress: ^0.21.6 => 0.21.6\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3195],{"name":3196,"color":3197},"build","377ba8",519,"nested templates not being compiled","2023-01-21T14:32:54Z","https://github.com/vuejs/vitepress/issues/519",0.6997731,{"description":3204,"labels":3205,"number":3206,"owner":3146,"repository":3147,"state":3148,"title":3207,"updated_at":3208,"url":3209,"score":3210},"### Is your feature request related to a problem? Please describe.\n\nNo\n\n### Describe the solution you'd like\n\nThe custom container are a very useful feature and it can be configurable in the .vitepress/config.js file with color for \r\nname,border, border-dark, background, background-dark in the config file with these 5 options i think it will make a better for a better blog points.\n\n### Describe alternatives you've considered\n\nHaving the lack of customization for the custom container boxes. I am aware that you can create components to do the same things but the \"::: name :::\" syntax is better to view in markdown as well as more read able than having it wrapped inside a html tag.\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] 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.",[],1246,"Adding Custom Containers from the config.js file ","2023-01-21T14:26:51Z","https://github.com/vuejs/vitepress/issues/1246",0.7074964,{"description":3212,"labels":3213,"number":3215,"owner":3146,"repository":3147,"state":3148,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### Describe the bug\r\n\r\nHi 👋🏻 \r\n\r\nI really liked the features like [Colored diff in code block](https://vitepress.dev/guide/markdown#colored-diffs-in-code-blocks) when introduced along with another features like code block focus mode.\r\n\r\nHowever, I was unable to use these features in Anu docs and today I also tried the same in my company's product documentaion but VitePress is unable to produce expected result.\r\n\r\nIf we grab the code snippet from official docs for \"Colored diff in code block\" our project's code snippet doesn't look same as VitePress's.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-fiz6gv?file=docs/example.md\r\n\r\n### Expected behavior\r\n\r\nCode block should look like as shown in VitePress site:\r\n\r\n\r\nHow it looks:\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 13.2.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 82.20 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.15.0/bin/yarn\r\n npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm\r\n Browsers:\r\n Chrome: 112.0.5615.137\r\n Firefox: 112.0\r\n Safari: 16.3\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.73 => 1.0.0-alpha.73\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nNone\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.",[3214],{"name":3165,"color":3166},2282,"🐞 Syntax highlighting using inline comment features aren't working","2023-05-02T00:04:03Z","https://github.com/vuejs/vitepress/issues/2282",0.70999587,{"description":3221,"labels":3222,"number":3227,"owner":3146,"repository":3147,"state":3148,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### 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.",[3223,3224],{"name":3176,"color":3177},{"name":3225,"color":3226},"has-workaround","1B4515",2567,"Code line numbers don't work well with text wrap","2023-07-10T00:05:11Z","https://github.com/vuejs/vitepress/issues/2567",0.7113132,{"description":3233,"labels":3234,"number":3236,"owner":3146,"repository":3147,"state":3148,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Describe the bug\r\n\r\n```md\r\n```js\r\n// [!code ++:4]\r\nconsole.log(1);\r\nconsole.log(1);\r\n\r\nconsole.log(1);\r\n\\```\r\n```\r\n\r\nRenders this following example:\r\n\r\n\r\n\r\nThis is due because a `\u003Cspan class=\"line diff add\">\u003C/span>` (line 3) is created without any content, if we change it to `\u003Cspan class=\"line diff add\"> \u003C/span>`, it now renders correctly.\r\n\r\n\r\n\r\nNot sure if a blank space is the best fix. \r\n\r\nAlso, should a line only containing `// [!code ++:4]` be highlighted as well? \r\n\r\n### Reproduction\r\n\r\nabove\r\n\r\n### Expected behavior\r\n\r\nto work normally\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)\r\n CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13600K\r\n Memory: 16.53 GB / 23.47 GB\r\n Container: Yes\r\n Shell: 5.8.1 - /usr/bin/zsh\r\n Binaries:\r\n Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node\r\n npm: 10.2.1 - ~/.nvm/versions/node/v20.9.0/bin/npm\r\n pnpm: 8.10.5 - ~/.nvm/versions/node/v20.9.0/bin/pnpm\r\n bun: 1.0.7 - ~/.bun/bin/bun\r\n npmPackages:\r\n vitepress: 1.0.0-rc.31 => 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.",[3235],{"name":3196,"color":3197},3305,"Colored Diffs in empty lines breaks + symbol","2024-01-08T00:04:50Z","https://github.com/vuejs/vitepress/issues/3305",0.7127288,["Reactive",3242],{},["Set"],["ShallowReactive",3245],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHxyM86RgiDzQFm_XqOoZdA-Bb-n7vmVYAQipMy8CdIU":-1},"/vuejs/vitepress/4921"]