This text, despite having\nline breaks in it, should still be\nrendered on a single line.\n\nBut it doesn't.\n```\nThis unexpectedly renders as follows:\n```\nTestComponent This text, despite having\n\nline breaks in it, should still be rendered on a single line.\n\nBut it doesn't.\n```\nNote that this does not happen if the Markdown line starts with a bit of text instead of with the Vue component:\n```md\nFor some reason, \u003CTestComponent /> this example\nrenders fine.\n```\n```\nFor some reason, TestComponent this example renders fine.\n```\n\n### Reproduction\n\n- Create a component with inline display style\n- Start a new Markdown paragraph with that component and continue across multiple Markdown lines\n - **There must be no text before the component**\n- The first line break within the Markdown source for that paragraph will render as an actual line break\n\nA repro is available here: https://stackblitz.com/edit/vite-xxlcwfge?file=docs%2Findex.md\n\n### Expected behavior\n\nThe line break in the Markdown source should not render as an actual line break. The example from above should render as follows:\n```\nTestComponent This text, despite having line breaks in it, should still be rendered on a single line.\n\nBut it doesn't.\n``` \n\n### System Info\n\n```Text\nSystem:\n OS: Windows 10 10.0.19045\n CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz\n Memory: 4.86 GB / 15.94 GB\n Binaries:\n Node: 22.14.0 - C:\\Program Files\\nodejs\\node.EXE \n npm: 10.9.2 - C:\\Program Files\\nodejs\\npm.CMD \n Browsers:\n Edge: Spartan (44.19041.3636.0), Chromium (127.0.2651.74)\n Internet Explorer: 11.0.19041.3636\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\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.",[2956],{"name":2957,"color":2958},"upstream","BF29ED",4626,"Markdown lines starting with an inline Vue component are incorrectly considered to be a whole paragraph","2025-04-10T13:10:53Z","https://github.com/vuejs/vitepress/issues/4626",0.7822113,{"description":2965,"labels":2966,"number":2967,"owner":2874,"repository":2875,"state":2923,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Is your feature request related to a problem? Please describe.\r\n\r\nPlease add on option where the public folder can be specified in build settings: https://vitepress.dev/reference/site-config#build\r\nThe public folder can be outside of `.vitepress` or `docs`\r\n\r\n### Describe the solution you'd like\r\n\r\nAlso, please add an option, that public folder can be specified in one, two or more instances and the output has to be combined in result. F.e.: project can have different folders: /imagesfromJohn, /simpleimages, /mybestimages/forsite\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\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.",[],2526,"`Public folder` outside of `.vitepress` or `docs`","2023-08-14T00:04:23Z","https://github.com/vuejs/vitepress/issues/2526",0.7823611,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fliX02TfevSJE7vExh55Ehx1c2xAFTbBhvRGoSCxwZFg":-1},"/vuejs/vitepress/2520"]