\u003C/svg>'\r\n }, link: 'https://gitlab.com/'}, title: 'my title link'\r\n ],\r\n```\r\n\r\nSee: typescript triggers \"cannot find name title\"\n\n### Expected behavior\n\n- ability to configure custom title element for each custom social link\r\n- default title for already available social networks\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.10 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz\r\n Memory: 11.38 GB / 12.31 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.1/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v16.15.1/bin/npm\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.49 => 1.0.0-alpha.49\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.",[2930],{"name":2931,"color":2932},"bug: pending triage","e99695",2081,"socialLinks items are not accessible","2023-03-21T00:03:57Z","https://github.com/vuejs/vitepress/issues/2081",0.70399034,{"description":2939,"labels":2940,"number":2941,"owner":2875,"repository":2876,"state":2886,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Is your feature request related to a problem? Please describe.\r\n\r\nMultiple sidebars do not work with multiple locales\r\n\r\nMultiple sidebars work only for the root locale\r\n\r\n```js\r\nimport sidebar_es from \"./sidebar.es\";\r\nimport sidebar_en from \"./sidebar.en\";\r\nimport sidebar_subdir_es from \"./sidebar.subdir.es\";\r\nimport sidebar_subdir_en from \"./sidebar.subdir.en\";\r\n\r\nexport default defineConfig({\r\n locales: {\r\n root: {\r\n lang: \"sp\",\r\n label: \"Spanish\",\r\n themeConfig: {\r\n nav: nav_es,\r\n sidebar: {\r\n \"/\": sidebar_es,\r\n \"/subdir/\": sidebar_subdir_es,\r\n },\r\n },\r\n },\r\n en: {\r\n lang: \"en\",\r\n label: \"English\",\r\n themeConfig: {\r\n nav: nav_en,\r\n sidebar: {\r\n \"/\": sidebar_en,\r\n \"/subdir/\": sidebar_subdir_en,\r\n },\r\n },\r\n```\r\n\r\nIn this example `/en/subdir/` path shows default `sidebar_en` sidebar\r\n\r\n### Describe the solution you'd like\r\n\r\nMultiple sidebars should work for secondary locales\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.",[],3202,"i18n and multiple sidebars problem","2023-11-21T00:04:49Z","https://github.com/vuejs/vitepress/issues/3202",0.7040141,{"description":2947,"labels":2948,"number":2949,"owner":2875,"repository":2876,"state":2886,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Is your feature request related to a problem? Please describe.\r\n\r\nCurrently Markdown is first-class in Vitepress in terms of asset-handling. Vue, frontmatter are second class.\r\n\r\nE.g. create a markdown page:\r\n\r\n~~~md\r\n\u003C!-- index.md -->\r\nThis is an image\r\n\r\n~~~\r\n\r\nVitepress parses into a Vue component, plus the image file is also added to the bundle pipeline for asset handling.\r\n\r\nCompare with a user-defined Vue component:\r\n\r\n~~~vue\r\n//MyImage.vue\r\n\u003Ctemplate>\r\n\u003Cimg :src=\"withPath(src)\">\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nimport { withPath } from 'vitepress'\r\nconst props = defineProps({ src: String })\r\n\u003C/script>\r\n~~~\r\n\r\n~~~md\r\n\u003C!-- index.md -->\r\nThis is an image defined as Vue component.\r\n\u003Cscript setup>\r\nimport MyImage from './components/MyImage.vue'\r\n\u003C/script>\r\n\r\n\u003CMyImage src=\"./image/myimage.png\" />\r\n~~~\r\n\r\nThe second case, Vitepress generates a target filename that is original source path with Base prepended. **But the filename is not the same as the Markdown-generated filename**. Also the image file is not added to the build.\r\n\r\nSame problem also happen to images referenced in frontmatter are also unprocessed by asset pipelines, e.g. HeroImage on the Home page.\r\n\r\nNew users of Vitepress are always confused about this --- e.g. see #505 and #301\r\n\r\n### Describe the solution you'd like\r\n\r\nOf course not every property or frontmatter string are assets, only some of them. \r\n\r\nHence the user should have a choice of which strings should be hashed and added to the asset pipeline.\r\n\r\nVitepress already provides a function \"withBase\" for customising URLs, but this is not enough for image assets. \r\n\r\nI would like to see user-callable functions that:\r\n- resolves the URL correctly in both Dev and Build cases\r\n- adds the file to the hash/build asset pipeline\r\n- and behaves correctly with the rest of Vite and Rollup \r\n\r\nThis will allow custom components to behave identically with Markdown, which is the original promise of Vitepress (i.e. \"every Markdown page is translated into a Vue SFC component\")\r\n\r\n### Describe alternatives you've considered\r\n\r\n1) The usual fallback of putting all images into \"public\" directory. Not an elegant solution.\r\n\r\n2) Defining path prefix constants in themeConfig. Does not resolve all user cases.\r\n\r\n3) Extending the Vite config to process extra directories. Two moving targets instead of one.\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] 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.",[],607,"My solution for custom components accessing relative assets -- Vite's static asset handling and enhanced Markdown hoisting","2023-01-21T16:04:03Z","https://github.com/vuejs/vitepress/issues/607",0.7052292,{"description":2955,"labels":2956,"number":2958,"owner":2875,"repository":2876,"state":2886,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Describe the bug\n\nActuall I am using one pakage in vue component and I am importing my vue component in vitepress then when I am trying to build I am getting this error\r\n\r\n(!) Some chunks are larger than 500 kBs after minification. Consider:\r\n\r\nUsing dynamic import() to code-split the application\r\nUse build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks\r\nAdjust chunk size limit for this warning via build.chunkSizeWarningLimit.\r\n✓ building client + server bundles...\r\n⠙ rendering pages...ReferenceError: document is not defined\r\nat enableDismissTrigger (C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:826:21)\r\nat C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:908:3\r\nat C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:7:83\r\nat Object. (C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:10:3)\r\nat Module._compile (node:internal/modules/cjs/loader:1101:14)\r\nat Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)\r\nat Module.load (node:internal/modules/cjs/loader:981:32)\r\nat Function.Module._load (node:internal/modules/cjs/loader:822:12)\r\nat ModuleWrap. (node:internal/modules/esm/translators:190:29)\r\nat ModuleJob.run (node:internal/modules/esm/module_job:185:25)\r\n✖ rendering pages...\r\nbuild error:\r\nReferenceError: document is not defined\r\nat enableDismissTrigger (C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:826:21)\r\nat C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:908:3\r\nat C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:7:83\r\nat Object. (C:\\ArunSk\\aswin\\node_modules\\bootstrap\\dist\\js\\bootstrap.js:10:3)\r\nat Module._compile (node:internal/modules/cjs/loader:1101:14)\r\nat Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)\r\nat Module.load (node:internal/modules/cjs/loader:981:32)\r\nat Function.Module._load (node:internal/modules/cjs/loader:822:12)\r\nat ModuleWrap. (node:internal/modules/esm/translators:190:29)\r\nat ModuleJob.run (node:internal/modules/esm/module_job:185:25)\r\nPS C:\\ArunSk\\aswin>\r\nif I comment that package and try to build it's building fine and I have added config.ts also\r\n\r\nimport { UserConfig } from 'vite';\r\n\r\nconst config: UserConfig = {\r\n// Other Vite configuration options...\r\nbuild: {\r\nrollupOptions: {\r\nexternal: /^bootstrap($|/)/,\r\n},\r\nssr: false,\r\n},\r\n};\r\n\r\nexport default config;\r\n\r\nmy package.json\r\n\r\n{\r\n\"scripts\": {\r\n\"docs:dev\": \"vitepress dev docs\",\r\n\"docs:build\": \"vitepress build docs\",\r\n\"docs:preview\": \"vitepress preview docs\"\r\n},\r\n\"peerDependencies\": {\r\n\"markdown-it-container\": \"^3.0.0\",\r\n\"vitepress\": \"\",\r\n\"vue\": \"^3.2.0\"\r\n},\r\n\"devDependencies\": {\r\n\"@types/markdown-it\": \"^12.2.3\",\r\n\"@types/markdown-it-container\": \"^2.0.5\",\r\n\"@types/node\": \"^18.16.3\",\r\n\"lint-staged\": \"^13.2.2\",\r\n\"vue\": \"^3.2.38\"\r\n},\r\n\"dependencies\": {\r\n\"bootstrap\": \"^5.2.0\",\r\n\"fire-stars\": \"^0.0.1\",\r\n\"markdown-it\": \"^13.0.1\",\r\n\"markdown-it-container\": \"^3.0.0\",\r\n\"sass\": \"^1.63.6\",\r\n\"vitepress\": \"\",\r\n\"vue\": \"^3.2.0\"\r\n}\r\n}\n\n### Reproduction\n\nSo is it possible to sort out that issue with vite config ts \r\n\r\n// vite.config.ts\r\nimport { defineConfig } from 'vite';\r\nimport { UserConfig } from 'vite';\r\n\r\nconst config: UserConfig = {\r\nbuild: {\r\nrollupOptions: {\r\nexternal: ['fire-stars'], // Add external module\r\noutput: {\r\nglobals: {\r\n'fire-stars': 'fireStars', // Provide global variable name for the external module\r\n},\r\n},\r\n},\r\n},\r\n};\r\n\r\nexport default defineConfig(config);\r\n\r\nso is it posiible with vite config ts file ?\n\n### Expected behavior\n\nBuild susseful \r\n\r\nAnd this is my old question same issue But now I want in diff approch\r\n\r\nhttps://github.com/vuejs/vitepress/issues/2633\n\n### System Info\n\n```sh\n{\r\n \"devDependencies\": {\r\n \"vitepress\": \"^1.0.0-beta.5\"\r\n },\r\n \"scripts\": {\r\n \"docs:dev\": \"vitepress dev vitepress\",\r\n \"docs:build\": \"vitepress build vitepress\",\r\n \"docs:preview\": \"vitepress preview vitepress\"\r\n },\r\n \"dependencies\": {\r\n \"fire-stars\": \"^0.0.1\",\r\n \"sass\": \"^1.63.6\"\r\n }\r\n}\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.",[2957],{"name":2931,"color":2932},2653,"Build issue ","2023-07-28T00:04:08Z","https://github.com/vuejs/vitepress/issues/2653",0.70588773,["Reactive",2964],{},["Set"],["ShallowReactive",2967],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmf7fRm4K6zg7k5fDV8-xHaI6112lqtNiap3yKpYDR0E":-1},"/vuejs/vitepress/510"]