\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n// import { useRoute } from \"vitepress\";\r\n// const route = useRoute();\r\n\u003C/script>\r\n```\r\n\r\n3. Create `docs/.vitepress/theme/index.js` with the following contents:\r\n\r\n```js\r\nimport Layout from \"./Layout.vue\";\r\n\r\nexport default {\r\n Layout,\r\n};\r\n```\r\n\r\n4. Run `yarn docs:dev` and open http://localhost:3000. Note the heading doesn't have any styles applied to it:\r\n\r\n\r\n\r\n5. Uncomment the lines in the `\u003Cscript setup>` section in `docs/.vitepress/theme/Layout.vue`. Note the heading now has the default styles applied to it, even though we only imported `useRoute`:\r\n\r\n\r\n\r\n**Expected behavior**\r\nThe heading should remain unstyled since we aren't explicitly importing any styles.\r\n\r\n**System Info**\r\n- vitepress version: v0.9.2\r\n- vite version: v1.0.0-rc.13\r\n- Node version: v12.20.0\r\n- OS version: macOS Catalina 10.15.7\r\n\r\n**Additional context**\r\nI had a quick look at the Vitepress code and it looks like the problem might be to do with this line: https://github.com/vuejs/vitepress/blob/309aa7a8d0e7ab08c1c9db258c74709a66b295cb/src/client/app/exports.ts#L29\r\n\r\nAdding the following to `docs/.vitepress/config.js`:\r\n\r\n```javascript\r\nmodule.exports = {\r\n alias: {\r\n \"/@default-theme/index\": \"/@theme/empty.js\",\r\n },\r\n};\r\n```\r\n\r\n...and creating an empty file `docs/.vitepress/theme/empty.js` prevents the default styles being applied.\r\n",[],182,"Importing default composables also imports default theme's styles","2023-01-21T16:23:59Z","https://github.com/vuejs/vitepress/issues/182",0.63032,{"description":2884,"labels":2885,"number":2889,"owner":2868,"repository":2869,"state":2870,"title":2890,"updated_at":2891,"url":2892,"score":2893},"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",[2886],{"name":2887,"color":2888},"docs","0075ca",157,"Recommended way to use Custom Vue components in .md","2023-01-21T16:04:10Z","https://github.com/vuejs/vitepress/issues/157",0.6416549,{"description":2895,"labels":2896,"number":2898,"owner":2868,"repository":2869,"state":2870,"title":2899,"updated_at":2900,"url":2901,"score":2902},"I'd like to only have a custom NavLinks component while keeping the default vitepress theme. Next I looked at the NavBar although also my version doesn't override. Any help in the right direction would be great.\r\n\r\ndocs/.vitepress/config.js\r\n\r\n```\r\nimport Theme from 'vitepress/theme'\r\nimport '../../assets/vars.css'\r\nimport NavBar from './Mynav.vue'\r\n\r\nconst MyTheme = {...Theme, Layout: {...Theme.Layout, NavBar}}\r\n\r\nexport default {\r\n ...MyTheme,\r\n NotFound: () => 'custom 404',\r\n enhanceApp({app, router, siteData}) {\r\n\r\n },\r\n}\r\n```\r\n ",[2897],{"name":2887,"color":2888},235,"Extending the vitepress theme","2023-03-18T00:04:16Z","https://github.com/vuejs/vitepress/issues/235",0.66191477,{"description":2904,"labels":2905,"number":2909,"owner":2868,"repository":2869,"state":2870,"title":2910,"updated_at":2911,"url":2912,"score":2913},"\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\nWhen I use the components directly in markdown file, It raised a waring with `vue.js:1099 [Vue warn]: Failed to resolve componen` as:\r\n\r\n\r\n\r\nDoes vitepress auto register components in `.vitepress/components`? or where can I put the `.vue` files and how to use them? thank you.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\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:\r\n- vite version:\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2906],{"name":2907,"color":2908},"bug: pending triage","e99695",60,"Is vitepress auto register components in `.vitepress/components`?","2023-01-21T16:25:31Z","https://github.com/vuejs/vitepress/issues/60",0.6626103,{"description":2915,"labels":2916,"number":2920,"owner":2868,"repository":2869,"state":2870,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Describe the bug\n\nI've been following the guide on how to set up Vitepress with a custom theme, and when I try to load a diferent vue file as a Layout it give me an error: \r\n\r\n> No loader is configured for \".vue\" files: docs/.vitepress/theme/Layout.vue\r\n\r\nWhat is more weird is that if I substitute that file with a function and and run serve the project in dev mode, while under HMR I can get it to work by replacing it back with the vue file.\n\n### Reproduction\n\nClone\r\n`git clone git@github.com:Beriu/blog.git`\r\n\r\nInstall Deps\r\n`cd blog && npm install`\r\n\r\nRun dev command\r\n`npm run docs:dev`\n\n### Expected behavior\n\nTo properly load the vue file\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 4.19 Ubuntu 20.04.1 LTS (Focal Fossa)\r\n CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz\r\n Memory: 7.84 GB / 12.36 GB\r\n Container: Yes\r\n Shell: 5.8 - /usr/bin/zsh\r\n Binaries:\r\n Node: 16.8.0 - ~/.nvm/versions/node/v16.8.0/bin/node\r\n npm: 7.21.0 - ~/.nvm/versions/node/v16.8.0/bin/npm\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.4 => 1.0.0-alpha.4\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2917],{"name":2918,"color":2919},"question","5D5FAE",1035,"Unable to load Layout.vue file (No loader is configured for \".vue\" files)","2023-01-21T14:30:16Z","https://github.com/vuejs/vitepress/issues/1035",0.66858524,{"description":2926,"labels":2927,"number":2929,"owner":2868,"repository":2869,"state":2870,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Describe the bug\n\nHello, awesome effort, looking forward to how this project grows.\r\n\r\nContext: adding documentation with Vitepress to a vue3 library that uses aliases inside `/@`. \r\n\r\nAdded `resolve.alias` using a `vite.config.ts` based on this https://github.com/vuejs/vitepress/issues/241 \r\n\r\nIt worked, but suddenly ignored completely the config on `docs/.vitepress/config.ts` (title, sidebar, nav, etc)\r\n\r\n```js\r\n// docs/.vitepress/config.ts\r\n\r\nmodule.exports = {\r\n title: 'Vue Dynamic Forms',\r\n description,\r\n themeConfig: {\r\n repo: 'asigloo/vue-dynamic-forms',\r\n logo: '/logo.svg',\r\n nav: [\r\n {\r\n text: 'Migration Guide',\r\n link: '/v3/guide/migration-guide',\r\n },\r\n ],\r\n sidebar: {\r\n '/': [\r\n {\r\n text: 'Guide',\r\n children: [\r\n {\r\n text: 'Introduction',\r\n link: '/guide/',\r\n },\r\n {\r\n text: 'Getting Started',\r\n link: '/guide/getting-started',\r\n },\r\n {\r\n text: 'Usage',\r\n link: '/guide/usage',\r\n },\r\n ],\r\n },\r\n ],\r\n },\r\n },\r\n}\r\n\r\n```\r\n\r\n\r\n\n\n### Reproduction\n\n- Add a `vite.config.ts` inside `docs` root \r\n- Add a `title`, also add `themeConfig`, `nav` or `sidebar` on `docs/.vitepress/config.ts` \r\n- Run `vitepress dev docs` \n\n### Expected behavior\n\n`vite.config.ts` `docs/.vitepress/config.ts` configs can live together \r\n\r\nor\r\n\r\nAn option to add `alias` to `docs/.vitepress/config.ts` \n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 11.4\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz\r\n Memory: 544.29 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 7.19.1 - ~/Projects/github/vue-dynamic-forms/node_modules/.bin/npm\r\n Browsers:\r\n Chrome: 92.0.4515.159\r\n Firefox: 89.0.1\r\n Safari: 14.1.1\r\n npmPackages:\r\n vitepress: ^0.16.1 => 0.15.6 \r\n```\n```\n\n\n### Additional context\n\n_No response_\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.",[2928],{"name":2907,"color":2908},373,"ThemeConfig is ignored when using vite.config.ts inside docs","2023-01-21T14:32:46Z","https://github.com/vuejs/vitepress/issues/373",0.67370164,{"description":2935,"labels":2936,"number":2937,"owner":2868,"repository":2869,"state":2870,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Is your feature request related to a problem? Please describe.\r\n\r\nMake configuration easier.\r\n\r\n### Describe the solution you'd like\r\n\r\nSame as [vite](https://vitejs.dev/config/#config-intellisense) :\r\n\r\n```ts\r\nimport { defineConfig } from 'vitepress'\r\n\r\nexport default defineConfig({\r\n lang: 'en-US',\r\n // ...\r\n}) \r\n``` \r\n\r\nBut we need to improve the support for theme config:\r\n\r\nBy default, `defineConfig` helper leverages the theme config type from default theme:\r\n\r\n```js\r\nimport { defineConfig } from 'vitepress'\r\n\r\nexport default defineConfig({\r\n themeConfig: {\r\n // Type is `DefaultTheme.Config` \r\n }\r\n})\r\n```\r\n\r\nIf you use a custom theme, you'll be able to pass the generics type for your custom theme, and you need overload it with the second parameter of `defineConfig` helper:\r\n\r\n```js\r\nimport { defineConfig } from 'vitepress'\r\nimport { ThemeConfig } from 'your-theme'\r\n\r\nexport default defineConfig\u003CThemeConfig>({\r\n themeConfig: {\r\n // Type is `ThemeConfig` \r\n }\r\n}, true); // declare `usingCustomTheme` and discard usage of the default theme.\r\n```\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/coc)\r\n- [X] Read the [docs](https://vitepress.vuejs.org/).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],464,"[Feature Request] Improve TypeScript support for config file.","2023-01-21T16:20:21Z","https://github.com/vuejs/vitepress/issues/464",0.67433393,{"description":2943,"labels":2944,"number":2945,"owner":2868,"repository":2869,"state":2870,"title":2946,"updated_at":2947,"url":2948,"score":2949},"How to do theme inheritance like VuePress in VitePress\r\n\r\nVuePress docs: https://vuepress.vuejs.org/theme/inheritance.html\r\n\r\nI would like to inherit the theme-default and change some component.\r\n\r\nThanks.",[],2102,"How to inherit theme","2023-03-17T13:23:25Z","https://github.com/vuejs/vitepress/issues/2102",0.6743666,{"description":2951,"labels":2952,"number":2953,"owner":2868,"repository":2869,"state":2870,"title":2954,"updated_at":2955,"url":2956,"score":2957},"\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\nCopying the configuration of vuepress to vitepress, the sidebar is not displayed as a result.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\nClone Repo: [https://github.com/misitebao/template-vitepress.git](https://github.com/misitebao/template-vitepress.git)\r\nRun: npm i && npm run dosc:dev\r\n\r\n**Expected behavior**\r\nDisplay the sidebar normally\r\n\r\n**System Info**\r\n- vitepress version: v0.12.2\r\n- vite version: \r\n- Node version: v14.8.0\r\n- OS version: Win10\r\n\r\n**Additional context**\r\nI want to implement a template template as the basis for subsequent vitepress projects\r\n",[],260,"Copying the configuration of vuepress to vitepress, the sidebar is not displayed as a result.","2023-01-21T16:22:24Z","https://github.com/vuejs/vitepress/issues/260",0.6744837,["Reactive",2959],{},["Set"],["ShallowReactive",2962],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHStsELSe3Rt8tMtfC0J0JQigZKJPzHpZBOeLmhvwAhQ":-1},"/vuejs/vitepress/58"]