ArcGIS\r\n details: Use the ArcGIS Maps SDK for JavaScript to build compelling web apps that unlock your data’s potential with interactive user experiences and stunning 2D and 3D visualizations.\r\n link: https://developers.arcgis.com/javascript/latest/\r\n target: \"_blank\"\r\n```\r\nIt runs well in dev, but when I deployed on gh-pages in a custom repository, the site comes like \\\u003Cusername\\>.github.io/\\\u003Crepo\\>/xxx.So I set base option in ./docs/.vitepress/config.mts, the logo.png runs well under this option.but in `index.md>home layout>features`,it didn't work.\r\nif add a \\\u003Crepo\\> before src link, worked but I should change it every time when add or remove a feature:\r\n```md\r\nfeatures:\r\n - title: \u003Cimg src= \"/gest_webgis/imgs/ArcGIS.png\" alt=\"ArcGIS\" class=\"inline-block\"/>ArcGIS\r\n details: Use the ArcGIS Maps SDK for JavaScript to build compelling web apps that unlock your data’s potential with interactive user experiences and stunning 2D and 3D visualizations.\r\n link: https://developers.arcgis.com/javascript/latest/\r\n target: \"_blank\"\r\n```\r\nHow can I use a `withBase` helper in vitepress within formatter in md files?\r\n\r\n### Reproduction\r\n\r\nwrite an img tag in `home layout > features>title`,set base option in ./docs/.vitepress/index.{js,mts}\r\n\r\n\r\n### Expected behavior\r\n\r\nthe /imgs/xxx.png should automatically change into ${baseUrl}/imgs/xxx.png at runtime or use withBase helper in home features\r\n\r\n### System Info\r\n\r\n```Text\r\nwin11, gitpub pages\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.",[3061],{"name":3062,"color":3063},"bug: pending triage","e99695",3139,"closed","How to use a `withBase` helper in vitepress within formatter in md files?","2023-11-02T00:04:19Z","https://github.com/vuejs/vitepress/issues/3139",0.69634384,{"description":3071,"labels":3072,"number":3073,"owner":3026,"repository":3027,"state":3065,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Is your feature request related to a problem? Please describe.\n\nLet's say we got a folder structure like this:\r\n\r\n\r\n└─ foo\r\n ├─ 1.0.0.md\r\n ├─ 2.0.0.md\r\n └─ 3.0.0.md\r\n\r\nRight now we would have routes like:\r\n `/foo/1.0.0.html`\r\n `/foo/2.0.0.html`\r\n `/foo/3.0.0.html`\r\n\r\nI'd like to also have a route or alias like the following: `/foo/latest` which will point to the latest version (this can all be determined on build time by looking at the file, I already have a function that gives me the latest \"route\", in this case `/foo/3.0.0.html`.\r\n\r\nHow can I make this `/foo/latest` route exist and be an alias to the one I wanted?\n\n### Describe the solution you'd like\n\nAllow us to define route aliases or redirects\n\n### Describe alternatives you've considered\n\nI've tried with rewrites but that allowed me to make the latest version redirected to /latest instead. I want the reverse.\n\n### Additional context\n\nIf this is not something you think vitepress should have because it's not SSG friendly (there is no latest.html file) then I understand.\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.",[],2922,"Route Alias or Redirect","2023-09-16T00:04:02Z","https://github.com/vuejs/vitepress/issues/2922",0.7172571,{"description":3079,"labels":3080,"number":3085,"owner":3026,"repository":3027,"state":3065,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Describe the bug\n\nWhen sidebar is not present, the page is not scrolled and outline is scrolled down, it overflows the navbar.\r\n\r\n \r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-v81ufa\r\n\r\n1. Make sure width is high enough so that outline is shown\r\n2. Without scrolling the main page content hover over the outline and scroll down\r\n3. Observe that the outline overflows the navbar\n\n### Expected behavior\n\nOutline is clipped when over navbar in the same way when sidebar is present.\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz\r\n Memory: 45.66 GB / 63.92 GB\r\n Binaries:\r\n Node: 18.2.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.5 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 9.6.6 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.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.",[3081,3082],{"name":3020,"color":3021},{"name":3083,"color":3084},"contribution welcome","11E4B8",2442,"Outline overflows navbar when sidebar not present","2023-08-16T00:04:22Z","https://github.com/vuejs/vitepress/issues/2442",0.7194739,{"description":3091,"labels":3092,"number":3098,"owner":3026,"repository":3027,"state":3065,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Is your feature request related to a problem? Please describe.\n\nCurrently, when you set `externalLinkIcon: true` it is not applied to the root `index.md`.\n\n### Describe the solution you'd like\n\nIt would be nice to also add the external link icon to external links in the root `index.md`.\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/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.",[3093,3094,3097],{"name":3020,"color":3021},{"name":3095,"color":3096},"has-workaround","1B4515",{"name":3023,"color":3024},4212,"Apply externalLinkIcon option to root index.md","2025-01-22T04:42:59Z","https://github.com/vuejs/vitepress/issues/4212",0.72962016,{"description":3104,"labels":3105,"number":3106,"owner":3026,"repository":3027,"state":3065,"title":3107,"updated_at":3108,"url":3109,"score":3110},"A packaging error occurred while using the Chinese Markdown filename\r\nyarn build\r\n\r\nyarn run v1.22.4\r\n$ vitepress build docs\r\nvitepress v0.11.5\r\nvite v2.0.0-beta.60\r\n- building client + server bundles...Language does not exist: sh\r\n✓ building client + server bundles...\r\n- rendering pages...Error: Cannot find module './%E5%85%B6%E4%BB%96%E7%AC%94%E8%AE%B0.md.js'\r\nRequire stack:\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\build\\render.js\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\build\\build.js\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\index.js\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\cli.js\r\n- E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\bin\\vitepress.js\r\n at Function.Module._resolveFilename (internal/modules/cjs/loader.js:982:15)\r\n at Function.Module._load (internal/modules/cjs/loader.js:864:27)\r\n at Module.require (internal/modules/cjs/loader.js:1044:19)\r\n at require (internal/modules/cjs/helpers.js:77:18)\r\n at E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:1659:12\r\n at loadPage (E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:75:18)\r\n at Object.go (E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:68:12)\r\n at Object.renderPage (E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\build\\render.js:18:12)\r\n at Object.build (E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\node\\build\\build.js:29:32) {\r\n code: 'MODULE_NOT_FOUND',\r\n requireStack: [\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\dist\\\\client\\\\app\\\\temp\\\\app.js',\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\dist\\\\node\\\\build\\\\render.js',\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\dist\\\\node\\\\build\\\\build.js',\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\dist\\\\node\\\\index.js',\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\dist\\\\node\\\\cli.js',\r\n 'E:\\\\item\\\\vue\\\\vite-build-test\\\\node_modules\\\\vitepress\\\\bin\\\\vitepress.js'\r\n ]\r\n}\r\n✖ rendering pages...\r\nbuild error:\r\n TypeError: Cannot destructure property 'frontmatter' of 'route.data' as it is null.\r\n at E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:1318:14\r\n at ComputedRefImpl.reactiveEffect [as effect] (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\reactivity\\dist\\reactivity.cjs.prod.js:46:24)\r\n at ComputedRefImpl.get value [as value] (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\reactivity\\dist\\reactivity.cjs.prod.js:774:32)\r\n at E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:1338:36\r\n at ComputedRefImpl.reactiveEffect [as effect] (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\reactivity\\dist\\reactivity.cjs.prod.js:46:24)\r\n at ComputedRefImpl.get value [as value] (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\reactivity\\dist\\reactivity.cjs.prod.js:774:32)\r\n at Object.unref (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\reactivity\\dist\\reactivity.cjs.prod.js:693:29)\r\n at E:\\item\\vue\\vite-build-test\\node_modules\\vitepress\\dist\\client\\app\\temp\\app.js:1347:71\r\n at renderComponentSubTree (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:208:13)\r\n at renderComponentVNode (E:\\item\\vue\\vite-build-test\\node_modules\\@vue\\server-renderer\\dist\\server-renderer.cjs.prod.js:174:16)\r\nerror Command failed with exit code 1.\r\ninfo Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.\r\n",[],217,"Cannot be packaged with file name in Chinese","2023-01-21T14:35:46Z","https://github.com/vuejs/vitepress/issues/217",0.7361838,{"description":3112,"labels":3113,"number":3117,"owner":3026,"repository":3027,"state":3065,"title":3118,"updated_at":3119,"url":3120,"score":3121},"I trying to create a dropdown with versions of my app, and remove (or add) elements based on this version. Anyone have example how to make it? or maybe its a proposal to make default in vite",[3114],{"name":3115,"color":3116},"duplicate","cfd3d7",1550,"[Question] How to create a dropdown version?","2023-01-21T14:22:48Z","https://github.com/vuejs/vitepress/issues/1550",0.73675036,{"description":3123,"labels":3124,"number":3125,"owner":3026,"repository":3027,"state":3065,"title":3126,"updated_at":3127,"url":3128,"score":3129},"related https://github.com/vuejs/vitepress/issues/628\r\n\r\nVitePress Next don't have this feature yet. Let's implement it. While doing so, I would also like to suggest new config structure for `locales` option.\r\n\r\nCurrently, we must define two `locales` when defining multi locale site. One in app config level, and one in theme config level.\r\n\r\nI think it's much easier to just be able to define locale on top level only.\r\n\r\n```js\r\nexport default {\r\n // Top level config for default and fallbacks.\r\n lang: 'en',\r\n title: 'VitePress',\r\n themeConfig: { ... }\r\n \r\n // All other locale settings.\r\n locales: {\r\n fr: {\r\n lang: 'fr',\r\n title: 'VitePress',\r\n themeConfig: { ... }\r\n },\r\n\r\n ja: {\r\n lang: 'ja',\r\n title: 'VitePress',\r\n themeConfig: { ... }\r\n }\r\n }\r\n}\r\n```\r\n\r\nThis should make typings much simpler too (maybe). It should eliminate weird situation like in #628 🤔 \r\n\r\nAlso, maybe not required for 1.0.0 release, but consider #291 as well.",[],631,"Add internationalization feature","2023-01-25T00:04:24Z","https://github.com/vuejs/vitepress/issues/631",0.73842937,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBwd2il7EodpiOPRhsCZeZ4xGIlmeunzaQQ9sfyCGxmQ":-1},"/vuejs/vitepress/2655"]