\r\n\u003Cbutton @click=\"clear\">clear all\u003C/button>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\n// ...\r\n import { ref } from 'vue';\r\n const editor = ref();\r\n\r\n const clear = () => {\r\n console.log(`editor.value`, editor.value);\r\n editor.value.setHtml();\r\n }\r\n\r\n\u003C/script>\r\n```\r\n\r\n# When using `defineClientComponent` it can't not found `setHtml`\r\n- `docs\\.vitepress\\theme\\index.js` config:\r\n```\r\nexport default {\r\n ...DefaultTheme,\r\n async enhanceApp(ctx) {\r\n const app = ctx.app;\r\n // ...\r\n if (!import.meta.env.SSR) {\r\n const Editor = defineClientComponent(() => {\r\n return import('../../../src/components/Editor.vue');\r\n })\r\n app.component('editor', Editor);\r\n }\r\n }\r\n}\r\n```\r\n- click `clear all` button\r\n- the result is :\r\n -:devtool tell me:editor.value.setHtml is not a function\r\n - `editor.value` object missing `setHtml` \r\n\r\n# When not using `defineClientComponent` it work normally\r\n- `docs\\.vitepress\\theme\\index.js` config:\r\n```\r\nimport Editor from '../../../src/components/Editor.vue'\r\nexport default {\r\n ...DefaultTheme,\r\n async enhanceApp(ctx) {\r\n const app = ctx.app;\r\n // ...\r\n if (!import.meta.env.SSR) {\r\n app.component('editor', Editor);\r\n }\r\n }\r\n}\r\n```\r\n- click `clear all` button\r\n- the result is :\r\n - editor.value.setHtml is called\r\n - console tab `editor.value` object has `setHtml` \r\n\r\n\r\n\r\n### Expected behavior\r\n\r\ndefineExpose works in defineClientComponent component\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz\r\n Memory: 1.18 GB / 7.86 GB\r\n Binaries:\r\n Node: 18.12.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files\\nodejs\\yarn.CMD\r\n npm: 8.19.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.43)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-rc.20 => 1.0.0-rc.20\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.",[2933],{"name":2892,"color":2893},3023,"can't get anything defined by `defineExpose` from component ref","2023-10-27T00:04:12Z","https://github.com/vuejs/vitepress/issues/3023",0.70116454,{"description":2940,"labels":2941,"number":2948,"owner":2869,"repository":2870,"state":2895,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Describe the bug\r\n\r\nIf I reference a PDF from a Markdown file like so:\r\n\r\n\r\n```md\r\nPlease see this [document](./doc.pdf)\r\n```\r\n\r\nAnd the `doc.pdf` lives in the same directory as the Markdown file, Vitepress does not process the PDF & add it to the `assetsDir` during build, resulting in `404` when the site is deployed. \r\n\r\nThe documentation on [Referencing Static Assets](https://vitepress.dev/guide/asset-handling#referencing-static-assets) seems to suggest it should. Am I missing something or is this not supported?\r\n\r\n(Right now I'm working round this by placing the file in the `/public` directory)\r\n\r\n### Reproduction\r\n\r\nExplained above.\r\n\r\n### Expected behavior\r\n\r\nI would expect the PDF to be available as an asset.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\r\n CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz\r\n Memory: 47.97 GB / 62.54 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 20.11.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 10.2.4 - /usr/bin/npm\r\n pnpm: 8.6.12 - ~/.local/share/pnpm/pnpm\r\n Browsers:\r\n Chrome: 121.0.6167.139\r\n Chromium: 121.0.6167.85\r\n npmPackages:\r\n vitepress: 1.0.0-rc.40 => 1.0.0-rc.40\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.",[2942,2945],{"name":2943,"color":2944},"docs","0075ca",{"name":2946,"color":2947},"contribution welcome","11E4B8",3535,"PDF not included in assets directory","2024-03-07T00:03:35Z","https://github.com/vuejs/vitepress/issues/3535",0.70419127,{"description":2954,"labels":2955,"number":2960,"owner":2869,"repository":2870,"state":2895,"title":2961,"updated_at":2962,"url":2963,"score":2964},"The site title gets wrapped when it's too long. I think we should set a max width and `text-overflow: ellipsis`.\r\n\r\nIt's happening on Vite's main branch doc => https://main.vitejs.dev\r\n\r\n\u003Cimg width=\"752\" alt=\"Screen Shot 2023-01-27 at 9 32 57\" src=\"https://user-images.githubusercontent.com/3753672/214981049-d230fb16-c948-4f57-b632-6648c8acaeae.png\">\r\n",[2956,2959],{"name":2957,"color":2958},"theme","0754FB",{"name":2866,"color":2867},1846,"Fix site title wrapping on layout home","2023-08-12T00:04:42Z","https://github.com/vuejs/vitepress/issues/1846",0.71339923,{"description":2966,"labels":2967,"number":2971,"owner":2869,"repository":2870,"state":2895,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Describe the bug\n\ni'm writting a doc using vitepress (v1.3.2) and i discovered VPTeamMembers components. \r\nSo i use those props:\r\n`// URL for the sponsor page for the member.\r\n sponsor?: string\r\n\r\n // Text for the sponsor link. Defaults to 'Sponsor'.\r\n actionText?: string`\r\n\r\nand wanted to change the default sponsor text but it didn't change. It still display sponsor.\n\n### Reproduction\n\n---\r\nlayout: page\r\n---\r\n```\u003Cscript setup>\r\nimport {\r\n VPTeamPage,\r\n VPTeamPageTitle,\r\n VPTeamMembers\r\n} from 'vitepress/theme'\r\n\r\nconst members = [\r\n {\r\n avatar: '/developpementLogo.jpg',\r\n name: 'Our Team',\r\n sponsor: 'www.google.fr',\r\n actionText: 'Discover' //it suppose to change 'Sponsor' into 'Discover'\r\n }\r\n]\r\n\u003C/script>\r\n\r\n\r\n\u003CVPTeamPage>\r\n \u003CVPTeamPageTitle>\r\n \u003Ctemplate #title>\r\n Our Team\r\n \u003C/template>\r\n \u003Ctemplate #lead>\r\n The development of VitePress is guided by an international\r\n team, some of whom have chosen to be featured below.\r\n \u003C/template>\r\n \u003C/VPTeamPageTitle>\r\n \u003CVPTeamMembers\r\n :members=\"members\"\r\n />\r\n\u003C/VPTeamPage>\r\n\n\n### Expected behavior\n\nit suppose to change Sponsor word like this but didn't work\r\n\r\n\r\n\r\n\n\n### System Info\n\n```Text\nSystem\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.",[2968],{"name":2969,"color":2970},"need more info","bdbefc",4124,"actionText prop on VPTeamMembers components doesn't works","2024-08-20T04:43:16Z","https://github.com/vuejs/vitepress/issues/4124",0.7170313,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6Yv0oLSqe9BE1AzdrGqXIjjJmOjI0GAXlsM5QwUu7PI":-1},"/vuejs/vitepress/551"]