\r\n```\r\n\r\nAlternatively, use the `desc` defined in the `container` to write Markdown syntax.\r\n\r\n```md\r\n::: demo src=\"../demo.vue\" title=\"Demo block\"\r\n\r\nThis is a `description` that can be written using Markdown.\r\n\r\n:::\r\n```\r\n\r\n### Describe the solution you'd like\r\n\r\nTo address this, I have created the [markdown-it-vitepress-demo](https://github.com/hairyf/markdown-it-vitepress-demo) plugin. I'm not sure if it can be helpful.\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- https://github.com/vuejs/vitepress/issues/987\r\n- https://github.com/vuejs/vitepress/issues/1349\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.",[2865],{"name":2866,"color":2867},"stale","ededed",2432,"vuejs","vitepress","open","feat(demo): built-in markdown plugin provides support for showcasing demo capabilities.","2024-07-17T14:37:26Z","https://github.com/vuejs/vitepress/issues/2432",0.710422,{"description":2877,"labels":2878,"number":2882,"owner":2869,"repository":2870,"state":2883,"title":2884,"updated_at":2885,"url":2886,"score":2887},"### Describe the bug\n\nStruggling to get [mermaid](https://mermaid-js.github.io/mermaid/#/) to work in vitepress through [markdown-it](https://github.com/markdown-it/markdown-it) plugin called [markdown-it-textual-uml](https://github.com/manastalukdar/markdown-it-textual-uml).\r\n\r\nGetting the following error output in console:\r\n```\r\nUncaught (in promise) ReferenceError: require is not defined\r\n at Proxy.mounted (index.md:6:9)\r\n at callWithErrorHandling (runtime-core.esm-bundler.js:155:22)\r\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:164:21)\r\n at Array.hook.__weh.hook.__weh (runtime-core.esm-bundler.js:2667:29)\r\n at flushPostFlushCbs (runtime-core.esm-bundler.js:356:32)\r\n at flushJobs (runtime-core.esm-bundler.js:401:9)\r\n```\n\n### Reproduction\n\nAdd markdown-it-textual-uml as an dependency - `npm install markdown-it-textual-uml --save`\r\n\r\nAnd add the following snippet to .vitepress/config.js\r\n```js\r\n markdown: {\r\n lineNumbers: true,\r\n config: (md) => {\r\n md.use(require(\"markdown-it-textual-uml\"));\r\n },\r\n },\r\n```\r\n\r\nAdd the following snippet to the index.md file with \r\n```js\r\n\u003Cscript>\r\nlet mermaid = null\r\nexport default {\r\n mounted() {\r\n if (mermaid == null) {\r\n mermaid = require('mermaid')\r\n }\r\n mermaid.initialize({\r\n startOnLoad: true,\r\n theme: 'forest'\r\n })\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\nAdd the following snippet in index.md\r\n```mermaid\r\ngraph TD;\r\n A-->B;\r\n A-->C;\r\n B-->D;\r\n C-->D;\r\n```\n\n### Expected behavior\n\nSee a mermaid graph load on index.md\r\n\r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.2\r\n CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz\r\n Memory: 92.18 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.13.2 - /usr/local/opt/node@16/bin/node\r\n Yarn: 1.22.11 - /usr/local/bin/yarn\r\n npm: 8.1.2 - /usr/local/opt/node@16/bin/npm\r\n Browsers:\r\n Chrome: 97.0.4692.99\r\n Safari: 15.3\r\n npmPackages:\r\n vitepress: ^0.21.6 => 0.21.6\n```\n\n\n### Additional context\n\n[Additional steps for mermaid to run in markdown-it-textual-uml](https://github.com/manastalukdar/markdown-it-textual-uml#additional-steps-for-mermaid)\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\n- [X] Read the [docs](https://vitepress.vuejs.org/).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2879],{"name":2880,"color":2881},"question","5D5FAE",518,"closed","Mount and Initialize mermaid via markdown-it-textual-uml as markdown-it plugin","2023-01-21T16:04:04Z","https://github.com/vuejs/vitepress/issues/518",0.6707989,{"description":2889,"labels":2890,"number":2894,"owner":2869,"repository":2870,"state":2883,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Describe the bug\r\n\r\nThe build and serve commands works but the dev doesn't.\r\n\r\n \r\n\r\n### Reproduction\r\n\r\nclone the [repo](https://github.com/emersonbottero/mermaid) \r\n- yarn build (you will get some post build error because I'm transitioning the documentation to vitepress)\r\n- yarn vdocs:build\r\n- yarn vdocs:serve (it works normally)\r\n- yarn vdocs:dev (it will thrown an error)\r\n\r\nThe error thrown is misleading in my opinion..\r\n\r\nUncaught TypeError: Cannot read properties of undefined (reading 'accept')\r\n at VPSkipLink.vue:37:3\r\n \r\n \r\n\r\n### Expected behavior\r\n\r\nthe error should point to the correct file?\r\nI'm sure is not a problem in VPSkipLink file.\r\nIs hard to debug without knowledge of vitepress internal logic \r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz\r\n Memory: 8.47 GB / 15.92 GB\r\n Binaries:\r\n Node: 16.13.2 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.5 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.1.3 - ~\\AppData\\Roaming\\npm\\npm.CMD\r\n Browsers:\r\n Chrome: 105.0.5195.127\r\n Edge: Spartan (44.22621.601.0), Chromium (105.0.1343.50)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.15 => 1.0.0-alpha.15\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI'm convincing the mermaidjs team to update their documentation to use vitepress 😁.\r\nI created a repo from scratch first and it works without problem but in the mermaid repo this error may be a combination of the setting done in packaeg.json and tsconfig but! \r\n\r\nI think we really want anyone to be able to use vitepress to update any library out there (mission inspiration?? 😅) \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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2891],{"name":2892,"color":2893},"build","377ba8",1395,"Not easy to debug error only in dev mode","2023-01-21T14:25:16Z","https://github.com/vuejs/vitepress/issues/1395",0.6896258,{"description":2900,"labels":2901,"number":2905,"owner":2869,"repository":2870,"state":2883,"title":2906,"updated_at":2907,"url":2908,"score":2909},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\n\r\nAdding a simple directive inside a markdown file or an SFC throws an error during the build. Seems like ClientOnly component does not exist yet in VitePress.\r\n\r\n`Custom directive is missing corresponding SSR transform and will be ignored.`\r\n\r\n**To Reproduce**\r\n\r\n\r\n```\r\n\u003Cdiv v-test>test\u003C/div>\r\n\r\n\r\n\u003Cscript>\r\nexport default {\r\n directives: {\r\n test: {\r\n mounted(el, binding) {\r\n console.log(el)\r\n }\r\n }\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\n\r\n**Expected behavior**\r\nBuild should work even though an SSR implementation for the custom directive doesn't exist.\r\n\r\n**System Info**\r\n- vitepress version: 0.6.0\r\n- vite version: v1.0.0-rc.4\r\n- Node version: 12.18.3\r\n- OS version: Catalina 10.15.6\r\n\r\n**Additional context**\r\nNone.\r\n",[2902],{"name":2903,"color":2904},"docs","0075ca",92,"Build fails due to custom directive missing an SSR Transform","2023-01-21T14:26:34Z","https://github.com/vuejs/vitepress/issues/92",0.70454323,{"description":2911,"labels":2912,"number":2914,"owner":2869,"repository":2870,"state":2883,"title":2915,"updated_at":2916,"url":2917,"score":2918},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\n\r\n```bash\r\n> vitepress build\r\n\r\nvitepress v0.7.3\r\nvite v1.0.0-rc.9\r\nbuilding client bundle...\r\nbuilding server bundle...\r\nrendering pages...\r\nbuild error:\r\n /*****/node_modules/vitepress/dist/client/app/temp/_assets/app.js:317\r\n nextProps[name] = ctx.slots[name]?.() ?? props[name];\r\n ^\r\n\r\nSyntaxError: Unexpected token '.'\r\n```\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n\r\n```typescript\r\nimport { computed, ComputedRef, SetupContext, VNode } from 'vue';\r\n\r\nexport function useReactLikeProps\u003CTProps extends Record\u003Cstring, any>>(\r\n component: any,\r\n props: TProps,\r\n ctx: SetupContext\u003Cany>,\r\n): ComputedRef\u003C\r\n TProps & {\r\n children?: VNode;\r\n }\r\n> {\r\n return computed(() => {\r\n const nextProps = { ...props };\r\n const VNodeProps: string[] = Object.keys(component.props).filter(name => {\r\n return (\r\n typeof component.props[name] === 'object' &&\r\n component.props[name].__TYPE__ === 'VNode'\r\n );\r\n });\r\n VNodeProps.forEach(name => {\r\n (nextProps as any)[name] = ctx.slots[name]?.() ?? props[name];\r\n });\r\n (nextProps as any).children = ctx.slots.default?.();\r\n return nextProps;\r\n });\r\n}\r\n```\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\n**System Info**\r\n- vitepress version: v0.7.3\r\n- vite version: v1.0.0-rc.9\r\n- Node version: v12.18.4\r\n- OS version: mac 10.15.7\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2913],{"name":2880,"color":2881},120,"build error: SyntaxError: Unexpected token '.'","2023-01-21T16:24:17Z","https://github.com/vuejs/vitepress/issues/120",0.70534027,{"description":2920,"labels":2921,"number":2923,"owner":2869,"repository":2870,"state":2883,"title":2924,"updated_at":2925,"url":2926,"score":2927},"I am looking into porting the using vue in Markdown from vuepress: \r\nhttps://vuepress.vuejs.org/guide/using-vue.html\r\n\r\nIf I understand correctly, vitepress doesn't want to auto register components by convention as Vuepress does. Is this the case? I actually liked this feature, but I understand that vitepress wants to keep the moving parts as small as possible.\r\n\r\nWhat is the recommended way to register the components? I see that in vue-router-next docs they are registered globally inside `enhanceApp`: https://github.com/vuejs/vue-router-next/search?q=HomeSponsors.\r\nSame as with this comment: https://github.com/vuejs/vitepress/issues/92#issuecomment-724645482\r\n\r\nShould we document this way in the docs?\r\n\r\nSome thoughts about this. It would be great that users that want to use the default theme as is, do not need to learn straight away about enhanceApp to be able to use a vue component in their markdown.\r\n\r\nIf auto registering by convention in a folder like `.vitepress/components` is not an option, could we import them directly in the markdown?\r\n\r\n```markdown\r\n# Docs\r\n\r\nThis is a .md using a custom component\r\n\r\n\u003CCustomComponent />\r\n\r\n## More docs\r\n\r\n...\r\n\r\n\u003Cscript setup>\r\n import CustomComponent from '../components/CustomComponent.vue'\r\n\u003C/script>\r\n```\r\n\r\nScript & style hoisting is working in vitepress: https://vuepress.vuejs.org/guide/using-vue.html#script-style-hoisting, but I tried this example to import a Component and it is not at this point.\r\n",[2922],{"name":2903,"color":2904},157,"Recommended way to use Custom Vue components in .md","2023-01-21T16:04:10Z","https://github.com/vuejs/vitepress/issues/157",0.7068614,{"description":2929,"labels":2930,"number":2932,"owner":2869,"repository":2870,"state":2883,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Discussed in https://github.com/vuejs/vitepress/discussions/1041\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **akil-rails** July 22, 2022\u003C/sup>\r\nThe [guide](https://vitepress.vuejs.org/guide/using-vue.html) explains:\r\n\r\n> To use code that assumes a browser environment on import, you need to dynamically import them in proper lifecycle hooks: how to use components th\r\n\r\n```vue\r\n\u003Cscript>\r\nexport default {\r\n mounted() {\r\n import('./lib-that-access-window-on-import').then((module) => {\r\n // use code\r\n })\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\nWhen the library is directly referenced (instead of a dependency), the load fails. Is this the expected behaviour? If so, the docs could mention that.\r\n\r\n`mermaid:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of \"text/html\". Strict MIME type checking is enforced for module scripts per HTML spec.`\r\n\r\n```vue\r\n\u003Cscript>\r\nexport default {\r\n mounted() {\r\n import('https://cdn.skypack.dev/mermaid').then((module) => {\r\n // use code\r\n })\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\u003C/div>\r\n\r\n\r\n### Steps to reproduce\r\n```\r\ngit clone git@github.com:akil-rails/vitepress-starter.git\r\ncd vitepress-starter\r\npnpm i\r\npnpm run docs:build\r\npnpm run docs:serve\r\n```\r\n1. Open the URL in chrome\r\n2. In chrome developer tools/console, you'll see the message \r\n```\r\nFailed to load module script: Expected a JavaScript module script but the server responded with a MIME type of \"text/html\". Strict MIME type checking is enforced for module scripts per HTML spec.\r\n```",[2931],{"name":2892,"color":2893},1042,"Dynamic Component with External Script - 'Failed to load module script:'","2023-01-21T14:30:10Z","https://github.com/vuejs/vitepress/issues/1042",0.7082578,{"description":2938,"labels":2939,"number":2943,"owner":2869,"repository":2870,"state":2883,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Describe the bug\r\n\r\nHi, I am trying to import and use a custom Markdown renderer inside a component but it looks like the `createMarkdownRenderer` function is not exported.\r\n\r\n```\r\nUncaught SyntaxError: The requested module '/@fs/Users/xyz/.github/xyz/node_modules/vitepress/dist/client/index.js?v=61ac765b' does not provide an export named 'createMarkdownRenderer' (at EndpointExample.vue:2:10)\r\n```\r\n\r\nHowever, according to TypeScript types exported from VitePress, `createMarkdownRenderer` should be available for use.\r\n\r\n### Reproduction\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { createMarkdownRenderer } from \"vitepress\";\r\n\r\nconst props = defineProps\u003C{\r\n requests: { type: string; content: string; }[];\r\n response: string;\r\n}>();\r\n\r\n// `createMarkdownRenderer` is not exported from vitepress.\r\nconst md = await createMarkdownRenderer(\".\");\r\nconst response = md.render(props.response);\r\n\u003C/script>\r\n```\r\n\r\n### Expected behavior\r\n\r\nThe function `createMarkdownRenderer` should be exported as it is available from TypeScript types. If it should not, then remove the `createMarkdownRenderer` type export.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 12.6\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 116.75 MB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\n Browsers:\r\n Brave Browser: 108.1.46.144\r\n Chrome: 108.0.5359.124\r\n Firefox: 103.0.2\r\n Safari: 16.0\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nPlease note that I am trying to create a custom `markdownRenderer` so that I can create a code render from my component props.\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2940],{"name":2941,"color":2942},"bug: pending triage","e99695",1752,"The requested module does not provide an export named 'createMarkdownRenderer'","2023-01-21T14:16:58Z","https://github.com/vuejs/vitepress/issues/1752",0.71036017,{"description":2949,"labels":2950,"number":666,"owner":2869,"repository":2870,"state":2883,"title":2951,"updated_at":2952,"url":2953,"score":2954},"## Description\r\nOn a Vue 3 beta 12 + VitePress 0.1.1 project, trying to build with `vitepress build` crashes with the following error\r\n\r\n## Output\r\n```\r\n$ vitepress build\r\nvitepress v0.1.1\r\nbuilding client bundle...\r\nbuilding server bundle...\r\nrendering pages...\r\nbuild error:\r\n ReferenceError: ssrRender is not defined\r\n at Object.\u003Canonymous> (/Users/marina/Developer/formvuelatte/node_modules/vitepress/lib/app/temp/_assets/index.js:621:22)\r\n at Module._compile (internal/modules/cjs/loader.js:1133:30)\r\n at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)\r\n at Module.load (internal/modules/cjs/loader.js:977:32)\r\n at Function.Module._load (internal/modules/cjs/loader.js:877:14)\r\n at Module.require (internal/modules/cjs/loader.js:1019:19)\r\n at require (internal/modules/cjs/helpers.js:77:18)\r\n at Object.renderPage (/Users/marina/Developer/formvuelatte/node_modules/vitepress/dist/build/render.js:12:27)\r\n at Object.build (/Users/marina/Developer/formvuelatte/node_modules/vitepress/dist/build/build.js:13:28)\r\n✨ Done in 3.61s.\r\n```\r\n\r\nThe line that seems to be crashing is line 12 in `node_modules/vitepress/dist/build/render.js`\r\n`const { createApp } = require(path_1.default.join(config.tempDir, '_assets/index.js'));`\r\n\r\n## Repo to reproduce\r\nTo reproduce you can check out: https://github.com/vuelidate/formvuelatte/tree/next",[],"Build throws error `ReferenceError: ssrRender is not defined`","2023-01-21T16:25:45Z","https://github.com/vuejs/vitepress/issues/12",0.7114628,{"description":2956,"labels":2957,"number":2959,"owner":2869,"repository":2870,"state":2883,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Describe the bug\r\n\r\nMy project is an es-modules-project (type=\"modules\" in package.json). I run Node v16.1.0.\r\n\r\nI added a `vite.config.ts` to my `/docs` folder to include WindiCSS in my Vitepress project:\r\n```ts\r\n// vite.config.ts\r\nimport { defineConfig } from 'vite';\r\nimport WindiCSS from 'vite-plugin-windicss';\r\n\r\nexport default defineConfig({\r\n plugins: [WindiCSS()],\r\n});\r\n```\r\n\r\nI use the environment variable `--experimental-specifier-resolution=node` for running the scripts:\r\n```\r\n// package.json\r\n{\r\n// ...\r\n \"scripts\": {\r\n \"docs:dev\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress dev docs\",\r\n \"docs:build\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress build docs\",\r\n \"docs:serve\": \"NODE_OPTIONS='--experimental-specifier-resolution=node' vitepress serve docs\"\r\n }\r\n// ...\r\n}\r\n```\r\n\r\ndocs:dev still works fine. But when I rund docs:build an error occurs:\r\n\r\n```sh\r\nfailed to load config from /home/project/docs/vite.config.ts\r\n✖ building client + server bundles...\r\nbuild error:\r\n Error: ENOENT: no such file or directory, unlink '/home/project/docs/vite.config.ts.js'\r\n at Object.unlinkSync (node:fs:1709:3)\r\n at loadConfigFromFile (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:71321:29)\r\n at async resolveConfig (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:70861:28)\r\n at async doBuild (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:38954:20)\r\n at async Object.build (/home/project/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-3d5f2596.js:38942:16)\r\n at async Promise.all (index 1)\r\n at async bundle (/home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js:40814:36)\r\n at async Object.build (/home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js:41015:59) {\r\n errno: -2,\r\n syscall: 'unlink',\r\n code: 'ENOENT',\r\n path: '/home/project/docs/vite.config.ts.js'\r\n}\r\n```\r\n\r\nIf I rename the `vite.config.ts` to `vite.config.js` it seems that the build process continues until the next error occurs:\r\n\r\n```sh\r\nError [ERR_REQUIRE_ESM]: Must use import to load ES Module: /home/chd/gettherapie-webseite/cim-elements/docs/.vitepress/.temp/app.js\r\nrequire() of ES modules is not supported.\r\nrequire() of /home/project/docs/.vitepress/.temp/app.js from /home/project/node_modules/vitepress/dist/node/serve-cf4b2162.js is an ES module file as it is a .js file whose nearest parent package.json contains \"type\": \"module\" which defines all .js files in that package scope as ES modules.\r\nInstead rename app.js to end in .cjs, change the requiring code to use import(), or remove \"type\": \"module\" from /home/project/docs/package.json.\r\n```\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nSee above\r\n\r\n### Expected behavior\r\n\r\nbuild should finish successfully\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 4.19 Ubuntu 20.04 LTS (Focal Fossa)\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\r\n Memory: 1.38 GB / 19.55 GB\r\n Container: Yes\r\n Shell: 5.0.16 - /bin/bash\r\n Binaries:\r\n Node: 16.1.0 - /usr/local/bin/node\r\n Yarn: 3.1.1 - ~/.yarn/bin/yarn\r\n npm: 7.11.2 - /usr/local/bin/npm\r\n npmPackages:\r\n vitepress: ^0.22.2 => 0.22.2\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nThe project runs under a yarn workspace monorepo\r\n\r\nIf I remove the vite.config.ts the build works fine.\r\n\r\n### Validations\r\n\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\r\n- [X] Read the [docs](https://vitepress.vuejs.org/).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2958],{"name":2892,"color":2893},537,"Build not working with vite.config.ts and es-modules","2023-01-21T14:25:14Z","https://github.com/vuejs/vitepress/issues/537",0.71223736,["Reactive",2965],{},["Set"],["ShallowReactive",2968],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmqS0J4R2yKtbX48Te_ErGjGSUgpNvrmPyghohc41ads":-1},"/vuejs/vitepress/2538"]