\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cp>Hello, world!\u003C/p>\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\n\r\nThen run `npx vitepress dev`, open http://localhost:5173/, and click on the green \"foo\" button that appears. VitePress gives a 404 error page. Reload the page, and the correct HTML page should appear with the contents \"Hello, world!\"\r\n\r\nGo back to http://localhost:5173/, and this time open the green \"foo\" button's link in a new tab. Observe that the page is loaded correctly with no 404.\r\n\r\n### Expected behavior\r\n\r\nVitePress should load the page correctly when clicking the link to open it in the current tab.\r\n\r\n### System Info\r\n\r\n```\r\nSystem:\r\n OS: macOS 12.6.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 277.38 MB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm\r\n Browsers:\r\n Chrome: 108.0.5359.98\r\n Firefox: 90.0\r\n Safari: 16.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.30 => 1.0.0-alpha.30\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] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],1685,"404 error when clicking link to public","2023-01-21T14:17:08Z","https://github.com/vuejs/vitepress/issues/1685",0.64108425,{"description":2887,"labels":2888,"number":2889,"owner":2871,"repository":2872,"state":2873,"title":2890,"updated_at":2891,"url":2892,"score":2893},"1. Put a file called `foo.json` in the `public/` directory\r\n2. In an `.md` file somewhere, create a link like `[look at this JSON file](/foo.json)`\r\n3. Build the site. The link works.\r\n4. Change the VitePress config to add `base: '/base/`\r\n5. Build the site again. The link doesn't work: it erroneously points to `/foo.json`, but it should point to `/base/foo.json`",[],1806,"Links to public/ files are wrong when a base URL is used","2023-02-20T00:04:34Z","https://github.com/vuejs/vitepress/issues/1806",0.67201185,{"description":2895,"labels":2896,"number":2901,"owner":2871,"repository":2872,"state":2873,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Describe the bug\n\nWhen you define a link to an image in frontmatter or in config.js, the file is note copy in the dist folder, whereas for a link in the markdown file directly it works, also when you define a public folder with your pictures it copy the content of the folder directly in dist folder and not in a public folder in dist folder. \n\n### Reproduction\n\nat this in a makdown file that represents the home page :\r\nfeatures:\r\n - icon: \r\n src: /public/compiler.png\r\ncreate a public folder in docs with the image\r\n\r\nand build the project\r\n\r\n\n\n### Expected behavior\n\nit will be preferable if the content of public folder will be copy in a dist/public folder, because here you can just enter :\r\nfeatures:\r\n - icon: \r\n src: compiler.png\r\n\r\nbut it is not very clear\n\n### System Info\n\n```sh\nnpm run docs:build\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.",[2897,2898],{"name":2868,"color":2869},{"name":2899,"color":2900},"stale","ededed",2422,"No inclusion of assets in frontmatter of markdown file and js config","2023-08-11T00:04:07Z","https://github.com/vuejs/vitepress/issues/2422",0.6735615,{"description":2907,"labels":2908,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"Vitepress keeps adding `.html` extension to any link referencing a pdf file relative to the page. Seems like it's hard-coded here\r\n\r\nhttps://github.com/vuejs/vitepress/blob/cee0b400d95b610fa47ea79007e03221a140084f/src/node/markdownToVue.ts#L52\r\n\r\nMay be it's the right way and any non-routed link should be put as `\u003Ca>` tag? Just wanted to share this observation.",[],265,"Adding link to (non-html) files from md","2023-01-21T16:20:09Z","https://github.com/vuejs/vitepress/issues/265",0.68009454,{"description":2915,"labels":2916,"number":2917,"owner":2871,"repository":2872,"state":2873,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Describe the bug\n\nI placed a `project.md` file in the public directory and want to link it in my markdown file to download it. I tried using the following markdown syntax:\r\n```\r\n[markdown file | download](/project.md){target=\"_self\" download}\r\n```\r\nHowever, after compilation, I noticed that the resulting HTML link was: \r\n```html\r\n\u003Ca href=\"/project.html\" target=\"_self\" download=\"\">markdown file | download\u003C/a>\r\n```\r\nSo, it seems that the link I set in my markdown page becomes an HTML page. \n\n### Reproduction\n\nJust see the \"Describe the bug\".\n\n### Expected behavior\n\nAfter compilation, the result should be as follows:\r\n```html\r\n\u003Ca href=\"/project.md\" target=\"_self\" download=\"\">markdown file | download\u003C/a>\r\n```\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.5\r\n CPU: (8) arm64 Apple M1\r\n Memory: 112.03 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.12.2 - /usr/local/bin/node\r\n npm: 10.5.0 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 125.0.6422.142\r\n Safari: 17.5\r\n npmPackages:\r\n vitepress: ^1.2.3 => 1.2.3\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.",[],3947,"Not support downloading local markdown file ","2024-06-16T04:41:53Z","https://github.com/vuejs/vitepress/issues/3947",0.68533033,{"description":2923,"labels":2924,"number":2926,"owner":2871,"repository":2872,"state":2873,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Describe the bug\n\nIf I enable localSearch in the theme config, markdown files in public dir are considered as if they are in the content dir and be processed by vitepress. This is unwanted.\n\n### Reproduction\n\nEnable localSearch and add markdown some files in the public dir.\n\n### Expected behavior\n\nPublic dir should not be processed by vitepress.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.19 Ubuntu 22.10 22.10 (Kinetic Kudu)\r\n CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz\r\n Memory: 4.08 GB / 7.21 GB\r\n Container: Yes\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.0.0 - ~/.local/share/pnpm/node\r\n npm: 9.6.2 - ~/.local/share/pnpm/npm\r\n Browsers:\r\n Chrome: 112.0.5615.49\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.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2925],{"name":2868,"color":2869},2209,"localSearch treat public dir as content","2023-04-20T00:03:59Z","https://github.com/vuejs/vitepress/issues/2209",0.68955135,{"description":2932,"labels":2933,"number":2937,"owner":2871,"repository":2872,"state":2873,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Describe the bug\r\n\r\nMainly described in the title, further description is at 4th point of reproducing the error. This is reproduced in normal python http server, and seems to happen in github pages as well.\r\n\r\nMight be related to #412, but I don't think its exactly the same behavior & cause.\r\n\r\n### Reproduction\r\n\r\n1. Download the repro and unzip, it should have the following content:\r\n\r\n```bash\r\n.\r\n├── content\r\n│ ├── first\r\n│ │ ├── index.md\r\n│ │ └── second.md\r\n│ └── index.md\r\n├── package.json\r\n└── yarn.lock\r\n```\r\n\r\n[vitepress-repro.zip](https://github.com/vuejs/vitepress/files/9575259/vitepress-repro.zip)\r\n\r\n\r\n2. Run `yarn && yarn run content:build`\r\n a `site` folder at project root should be created.\r\n4. Run `python3 -m http.server -d . 4000`, and lookup `localhost:4000/site`.\r\n Everything looks fine, you can navigate to First using navbar, and second.md file in first by left panel.\r\n5. Now refresh at the same `localhost:4000/site/first/second`.\r\n You should see the page is loaded but a 404 page is added at the bottom too, now if you try to navigate, the top of page remains as is, the bottom of page is instead replaced by the new content.\r\n\r\n### Expected behavior\r\n\r\nPage should not append a 404 page, nor it should load navigated pages in bottom of page instead of replacing current page.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.18 Void\r\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\r\n Memory: 3.97 GB / 7.56 GB\r\n Container: Yes\r\n Shell: 3.5.1 - /usr/bin/fish\r\n Binaries:\r\n Node: 16.15.1 - /usr/bin/node\r\n Yarn: 1.22.18 - /usr/bin/yarn\r\n npm: 8.11.0 - /usr/bin/npm\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nFull page screenshot\r\n\r\n\r\n\r\nTwo errors, in order appears in the browser's console:\r\n\r\n```\r\nFailed to load resource: the server responded with a status of 404 (File not found) :4000/site/assets/first_second_index.md.undefined.lean.js:1\r\n\r\nHydration completed but contains mismatches. app.558d10a0.js:1\r\n```\r\n\r\nPoint to be noted is that `first_second_index.md.undefined.lean.js` is trying to get fetched, i.e. the \"undefined\" hash.\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.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2934],{"name":2935,"color":2936},"need more info","bdbefc",1345,"Built content when served manually (not `vitepress dev \u003Csrc>`) adds a 404 page at end of page, and later navigation loads the page there at bottom replacing 404 at the bottom.","2023-01-21T14:25:22Z","https://github.com/vuejs/vitepress/issues/1345",0.69845825,{"description":2943,"labels":2944,"number":2945,"owner":2871,"repository":2872,"state":2873,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the bug\r\n\r\nIf you include one or more Markdown files in another page, the local search index \"sees them all\" as separate pages - i.e. not as 1 single page which can be navigated to via the local search box. \r\n\r\n### Reproduction\r\n\r\n1. Add the following Markdown files to a Vitepress project\r\n\r\n **part_1.md**\r\n ```\r\n Hello\r\n ```\r\n \r\n **part_2.md**\r\n ```\r\n World\r\n ```\r\n \r\n **index.md**\r\n ```\r\n \u003C!--@include: ./part_1.md-->\r\n \r\n \u003C!--@include: ./part_2.md-->\r\n ```\r\n \r\n2. Configure local search and search for the word \"Hello\".\r\n\r\n\r\n### Expected behavior\r\n\r\nGiven the example above, I would expect:\r\n\r\n1. It is not possible to navigate to `part_1.md` or `part_2.md` pages at all.\r\n2. Searching for the word \"Hello\" will show `index.md` as the only result.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 6.2 Ubuntu 23.04 23.04 (Lunar Lobster)\r\n CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz\r\n Memory: 55.33 GB / 62.54 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 18.17.1 - /usr/bin/node\r\n npm: 9.6.7 - /usr/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.96\r\n Chromium: 116.0.5845.96\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.4 => 1.0.0-rc.4 \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.",[],2812,"process includes before creating search index","2023-09-18T00:04:21Z","https://github.com/vuejs/vitepress/issues/2812",0.7025056,{"description":2951,"labels":2952,"number":2954,"owner":2871,"repository":2872,"state":2873,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Describe the bug\r\n\r\nAccording to https://vitepress.dev/guide/asset-handling#base-url , if files are in public you should not have to adjust for the base URL. However I have an iframe in public that only works if the base url is not set.\r\n\r\n```html\r\n\u003Ciframe src=\"/config/failsafe/index.html\" frameborder=\"0\" height=\"1400px\" style=\"text-align: center; margin-left: -230px; margin-right: -230px;\" width=\"1200\">\u003C/iframe>\r\n```\r\n\r\nIf the base url is set then I get an error asking me whether I meant the file in the base URL.\r\n\r\n### Reproduction\r\n\r\nI can create a cut down starter if needed. \r\n\r\n### Expected behavior\r\n\r\n`/config/failsafe/index.html` above should be found irrespective of the base URL.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 11 10.0.22621\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz\r\n Memory: 17.59 GB / 31.83 GB\r\n Binaries:\r\n Node: 19.8.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files\\nodejs\\yarn.CMD\r\n npm: 9.5.1 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 8.12.0 - C:\\Program Files\\nodejs\\pnpm.CMD\r\n Browsers:\r\n Edge: Chromium (120.0.2210.61)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.25 => 1.0.0-rc.25\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI tried adding this using an inline script. That \"works\" but the script appears to be reordered before the rest of the markdown, so I can't choose where to insert the element other than body, because any elements I add to markdown do not exist when this is run.\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.",[2953],{"name":2868,"color":2869},3318,"iframe source in public not being adjusted for base URL","2023-12-19T00:04:39Z","https://github.com/vuejs/vitepress/issues/3318",0.70605266,["Reactive",2960],{},["Set"],["ShallowReactive",2963],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyl0xuqioGRQLcOYuiB_YNjT6ALFZaTIOSrlUi5gE_K8":-1},"/vuejs/vitepress/360"]