```\r\n\r\nIt doesn't seem to be correct:\r\n\r\n\r\n\r\nHow to make it look correct, just like on the homepage?:\r\n\r\n\r\n\r\n",[2915],{"name":2869,"color":2870},4273,"How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.76538587,{"description":2922,"labels":2923,"number":2928,"owner":2872,"repository":2873,"state":2929,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Describe the bug\n\n- Blockquotes can be nested.\r\n- Custom blocks can be nested.\r\n- But GitHub-flavored alerts cannot (with errors).\r\n\r\n```md\r\n> case 1\r\n>\r\n> > nested content\r\n\r\n:::: tip\r\ncase 2\r\n\r\n::: warning\r\nnest content\r\n:::\r\n::::\r\n\r\n> [!TIP]\r\n> case 3\r\n>\r\n> > [!WARNING]\r\n> > case 3\r\n```\r\n\r\n\r\n\r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-alzhrt?file=docs%2Fexample.md\n\n### Expected behavior\n\nRender without errors.\n\n### System Info\n\n```Text\nN/A\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.",[2924,2925],{"name":2866,"color":2867},{"name":2926,"color":2927},"contribution welcome","11E4B8",3512,"closed","Bug: GitHub-flavored alerts cannot be nested (with errors)","2024-02-11T00:04:59Z","https://github.com/vuejs/vitepress/issues/3512",0.72119373,{"description":2935,"labels":2936,"number":2937,"owner":2872,"repository":2873,"state":2929,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Describe the bug\n\nvitepress dev is normal, but vitepress build reports an error, SyntaxError: Element is missing end tag. The key is that it is impossible to locate where the end tag is missing.\n\n### Reproduction\n\nvitepress build\n\n### Expected behavior\n\nPack normally or provide specific error information\n\n### System Info\n\n```Text\n\"vitepress\": \"^1.1.4\"\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.",[],3876,"SyntaxError: Element is missing end tag.","2024-05-31T04:42:05Z","https://github.com/vuejs/vitepress/issues/3876",0.7225045,{"description":2943,"labels":2944,"number":2946,"owner":2872,"repository":2873,"state":2929,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Describe the bug\r\n\r\nYou can check Reproduction Url test.\r\n\r\nEverything works fine when I start the vite project(`apps/playground`) using `pnpm dev:playground`. It crashed when I started vitepress project(`apps/document`) using `pnpm dev:document`.\r\n\r\nMy monorepo project uses `node condition` to link the source code. You can check the `dev` field in `package.json` or `condition: [\"dev\"]` in `vite.config.ts` or `condition: [\"dev\"]` in `config.ts`.\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/i7eo/monorepo-vitepress-bug-report\r\n\r\n### Expected behavior\r\n\r\nStart normally like a vite project(`apps/playground`)\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.4.1\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 3.61 GB / 64.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node\r\n npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm\r\n pnpm: 9.1.0 - ~/.nvm/versions/node/v20.12.2/bin/pnpm\r\n Watchman: 2024.04.08.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Chrome: 124.0.6367.201\r\n Safari: 17.4.1\r\n Safari Technology Preview: 17.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.",[2945],{"name":2905,"color":2906},3888,"Vitepress project in monorepo reports `Failed to resolve import \"xxx\"`","2024-05-22T04:41:52Z","https://github.com/vuejs/vitepress/issues/3888",0.7308569,{"description":2952,"labels":2953,"number":2954,"owner":2872,"repository":2873,"state":2929,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Is your feature request related to a problem? Please describe.\n\nI use page hrefs in dynamic `\u003Cmeta>` tags, for example in `og:url`. It'd be great if VitePress provided a way to reliably reference the page's pathname, to ensure that that part of the dynamic meta content is correct.\n\n### Describe the solution you'd like\n\nExport this function: https://github.com/vuejs/vitepress/blob/452d6c77a6afa43faa245452e7d0b360e55a36fb/src/shared/shared.ts#L65\r\n\n\n### Describe alternatives you've considered\n\nCurrently, I copy `normalize`, `HASH_OR_QUERY_RE`, and `INDEX_OR_EXT_RE` from `src/shared/shared.ts` to my VitePress config. That's brittle and inelegant.\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.",[],4401,"feature request: export src/shared/shared's normalize()","2025-01-28T04:42:53Z","https://github.com/vuejs/vitepress/issues/4401",0.74126226,{"description":2960,"labels":2961,"number":2965,"owner":2872,"repository":2873,"state":2929,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Describe the bug\n\nMy project add network request, But I need different environment variables control the request address, how should I use env in vite\r\n\r\n[Env Variables](https://vitejs.dev/guide/env-and-mode.html#env-variables)\n\n### Reproduction\n\nNone\n\n### Expected behavior\n\nI want to be able to access `import.meta.env.BASE_URL`, just like the vite project\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11 10.0.22631\r\n CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12600KF\r\n Memory: 2.31 GB / 31.82 GB\r\n Binaries:\r\n Node: 18.19.0 - D:\\software\\nodejs\\node.EXE\r\n npm: 10.2.3 - D:\\software\\nodejs\\npm.CMD\r\n pnpm: 9.1.1 - ~\\AppData\\Local\\pnpm\\pnpm.CMD\r\n bun: 1.1.3 - ~\\.bun\\bin\\bun.EXE\r\n Browsers:\r\n Edge: Chromium (123.0.2420.97)\r\n Internet Explorer: 11.0.22621.3527\r\n npmPackages:\r\n vitepress: 1.0.2 => 1.0.2\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.",[2962],{"name":2963,"color":2964},"need more info","bdbefc",3896,"How to using Vite Env Variables?","2024-05-24T04:42:25Z","https://github.com/vuejs/vitepress/issues/3896",0.7421388,["Reactive",2971],{},["Set"],["ShallowReactive",2974],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fL14XQUw1DSjF-agDKqz6T6VJT_UXMx-EaR_p_8ZwdVs":-1},"/vuejs/vitepress/3728"]