\r\n\u003C/div>\r\n`\r\n\r\n// when creating a demo section, `@/` will be replaced with `srcDir`\r\nexport const demoPlugin = (md: MarkdownIt, srcDir: string) => {\r\n const parser: RuleBlock = (state, startLine, _endLine, _silent) => {\r\n /*... some code to extract the file name from the markdown ... */\r\n token.attrSet('src', resolve(filename))\r\n return true\r\n }\r\n\r\n const renderer: RenderRule = (...args) => {\r\n /* ... some code to get `src` and check that the file exists ... */\r\n \r\n const file = readFileSync(src, 'utf8')\r\n\r\n // script\r\n token.info = `ts`\r\n token.content = findSection(file, SCRIPT_START, SCRIPT_END)\r\n const script = md.renderer.rules.fence!(...args)\r\n\r\n // template\r\n token.info = `vue-html`\r\n token.content = findSection(file, TEMPLATE_START, TEMPLATE_END)\r\n const template = md.renderer.rules.fence!(...args)\r\n\r\n // component\r\n const demo = md.render(COMPONENT_SNIPPET(src))\r\n\r\n return script + template + demo\r\n }\r\n\r\n md.renderer.rules.demo = renderer\r\n md.block.ruler.before(md.block.ruler.getRules('')[0].name, 'demo', parser)\r\n}\r\n\r\n// returns everything between the first match of `start` and the subsequent first match for `end`\r\nfunction findSection(content: string, start: RegExp, end: RegExp): string {\r\n //...\r\n}\r\n``` \r\n\r\nSo the markdown rendered used to take the line `const demo = md.render(COMPONENT_SNIPPET(src))` and automagically put the `import` statement where it needs to be and happily render the component. However, since updating to `1.0.0-alpha.11` this no longer works. In fact if I manually write out the import statement in the markdown file, everything works - so something is wrong with the way my plugin is handling the import.\r\n\r\nI looked into the way [plugin-sfc](https://github.com/mdit-vue/mdit-vue/tree/main/packages/plugin-sfc) works and it looks like there was a change from `0.10.0` to `0.11.0` in the way script SFC blocks are handled.\r\n\r\nI tried to copy the way the changed code works in my plugin, but I have not managed to get it working:\r\n\r\n```ts\r\n const block = `\u003Cscript setup lang=\"ts\"> import DemoComponent from \"${src}\"; \u003C/script>`\r\n sfcBlocks.scriptSetup = block\r\n sfcBlocks.scripts.push(block)\r\n\r\n token.content = `\u003Cdiv class=\"vp-raw\"> \u003Cdemo-component/> \u003C/div>`\r\n const demo = md.renderer.rules.html_block!(...args)\r\n```\r\n\r\nDoes anyone know how this can be done? How can my plugin tell VitePress that it needs to import the demo component for this page?\r\n",[],1349,"Import custom component in MarkdownIt plugin","2023-01-21T14:22:46Z","https://github.com/vuejs/vitepress/issues/1349",0.68538755,{"description":2921,"labels":2922,"number":2926,"owner":2860,"repository":2861,"state":2896,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Is your feature request related to a problem? Please describe.\r\n\r\nWe recently migrated our site https://grammy.dev from VuePress 2 to VitePress, and we adjusted the configuration for the Algolia crawler according to their example at https://docsearch.algolia.com/docs/templates/#vitepress-template. However, this config yields almost 60 % fewer records for the search index in comparison with the VuePress config on the old VuePress site.\r\n\r\n### Describe the solution you'd like\r\n\r\nPublish the config you use for the Algolia crawler, or publish a different example config. Ideally, it should be included here: https://vitepress.dev/reference/default-theme-search#algolia-search\r\n\r\n### Describe alternatives you've considered\r\n\r\nWait for Algolia to update their docs, which I am not sure when it will happen. VitePress moves quickly, and I am not sure how well they are able to keep up with their docs. You guys know your site best, so it will be helpful to have a VitePress-recommended crawler config.\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.",[2923],{"name":2924,"color":2925},"docs","0075ca",2592,"Provide example Algolia crawler configuration in the docs","2023-07-27T00:04:26Z","https://github.com/vuejs/vitepress/issues/2592",0.7060705,{"description":2932,"labels":2933,"number":2934,"owner":2860,"repository":2861,"state":2896,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Is your feature request related to a problem? Please describe.\n\nsome function in `frontmatter.title`, like below:\r\n\r\n```markdown\r\n---\r\nlayoutClass: a-home-layout\r\ntitle: ${{ getWishNameStr(GameName.ZZZ) }}时间轴\r\noutline: false\r\naside: false\r\nsidebar: false\r\ndoc: false\r\nfooter: false\r\n---\r\n```\r\n\r\n\u003Cimg width=\"532\" alt=\"123\" src=\"https://github.com/vuejs/vitepress/assets/34206897/6fd4f405-dddb-46d1-a164-7dee1aaa476f\">\r\n\n\n### Describe the solution you'd like\n\nThe page title should be the result of the calculation. In this case it should be: `调频时间轴 | Augus Game`\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.",[],4025,"What if I use the function in frontmatter?","2024-07-15T04:43:22Z","https://github.com/vuejs/vitepress/issues/4025",0.7159268,{"description":2940,"labels":2941,"number":2942,"owner":2860,"repository":2861,"state":2896,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Describe the bug\n\n当我按顺序引入js脚本的时候,后面的脚本依赖于前面的,问题入下图\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-yl3bnx\n\n### Expected behavior\n\n预期是不会产生 is not defined. 这个错误\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 12.3.1\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz\r\n Memory: 147.43 MB / 16.00 GB\r\n Shell: 3.2.57 - /bin/sh\r\n Binaries:\r\n Node: 20.0.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.6.4 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 117.0.5938.62\r\n Safari: 15.4\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.13 => 1.0.0-rc.13\n```\n\n\n### Additional context\n\n\u003Cimg width=\"521\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/17758990/61b1827b-79f7-4b89-8db4-29061ba08a02\">\r\n\u003Cimg width=\"649\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/17758990/4757b2c1-35b6-4336-bd4a-f9731418dc82\">\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.",[],2966,"head 引入脚本提示未定义","2023-09-23T00:04:04Z","https://github.com/vuejs/vitepress/issues/2966",0.7165678,{"description":2948,"labels":2949,"number":2953,"owner":2860,"repository":2861,"state":2896,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Is your feature request related to a problem? Please describe.\r\n\r\nConveniently use content-adaptive layout in components on the home page\r\n\r\n### Describe the solution you'd like\r\n\r\n`.vitepress/theme/index.ts`:\r\n```ts\r\nimport HomePage from './component/HomePage'\r\n\r\nexport default {\r\n Layout: () => {\r\n return h(Theme.Layout, null, {\r\n 'home-features-after': () => h(HomePage),\r\n })\r\n },\r\n```\r\n\r\n---\r\n\r\n`HomePage.vue`:\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport{ VPHomeContent } from 'vitepress/theme'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n\t\u003CVPHomeContent>\r\n\t\t\u003C!-- my custom content -->\r\n\t\u003C/VPHomeContent>\r\n\u003C/template>\r\n```\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.",[2950],{"name":2951,"color":2952},"contribution welcome","11E4B8",3954,"[New feature] export `VPHomeContent` to provide content-adaptive layout","2024-06-22T04:41:46Z","https://github.com/vuejs/vitepress/issues/3954",0.7173621,["Reactive",2959],{},["Set"],["ShallowReactive",2962],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1WBGuj2f3tb2FTL6QFQl-8ngxCcUzqLVc-h2EdMxdGs":-1},"/vuejs/vitepress/4133"]