\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.69200593,{"description":2885,"labels":2886,"number":2890,"owner":2869,"repository":2870,"state":2871,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Describe the bug\n\nwhen I bump vitepress to `1.0.0-rc.26`, I found the styles in `\u003Cstyle>` were not included in the packaged product.\r\n\r\n The style here is normal in the development environment, but it doesn't work after packing.\r\n\r\n``` vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"box\">Preview after packing, The text color is expected to be red\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle>\r\n.box {\r\n color: red;\r\n}\r\n\u003C/style>\r\n``` \r\n\r\nI try downgraded to `1.0.0-rc.25`, it was normal.\n\n### Reproduction\n\nreproduction link:\r\n[https://stackblitz.com/edit/vite-xmetfv?file=docs%2FDemo.vue](https://stackblitz.com/edit/vite-xmetfv?file=docs%2FDemo.vue)\r\n\n\n### Expected behavior\n\nPackaged for preview and styles can also take effect\r\n\r\nrelated documents:\r\n[https://vitepress.dev/guide/using-vue#script-and-style](https://vitepress.dev/guide/using-vue#script-and-style)\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)\r\n CPU: (16) x64 AMD Ryzen 7 4800H with Radeon Graphics\r\n Memory: 6.16 GB / 7.44 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node\r\n Yarn: 1.22.19 - /mnt/c/Program Files/nodejs/yarn\r\n npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm\r\n pnpm: 8.10.5 - ~/.nvm/versions/node/v18.18.2/bin/pnpm\r\n bun: 1.0.12 - ~/.nvm/versions/node/v18.18.2/bin/bun\r\n npmPackages:\r\n vitepress: 1.0.0-rc.26 => 1.0.0-rc.26\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.",[2887],{"name":2888,"color":2889},"build","377ba8",3216,"Using SFC in markdown, styles in the `\u003Cstyle>` tag is not effect.","2023-11-25T00:04:34Z","https://github.com/vuejs/vitepress/issues/3216",0.69805264,{"description":2896,"labels":2897,"number":2904,"owner":2869,"repository":2870,"state":2871,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Is your feature request related to a problem? Please describe.\n\nIt would be nice to have the latest version of Inter for VitePress\n\n### Describe the solution you'd like\n\nI'd love if the `woff` files of the font would be update it to the latest version (4). The last change to those files were 2 years ago, way before version 4.\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.",[2898,2901],{"name":2899,"color":2900},"theme","0754FB",{"name":2902,"color":2903},"contribution welcome","11E4B8",3693,"Update Inter font family to version 4","2024-04-28T12:25:11Z","https://github.com/vuejs/vitepress/issues/3693",0.7016036,{"description":2910,"labels":2911,"number":2915,"owner":2869,"repository":2870,"state":2871,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Is your feature request related to a problem? Please describe.\r\n\r\nWhen I use Element-Plus in VitePress, the partial style of the component is modified. The reason is VitePress `src/client/theme-default/styles/layout.css` File reset all styles.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nI hope this code only takes effect in VitePress.\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.",[2912],{"name":2913,"color":2914},"duplicate","cfd3d7",434,"This is a suggestion","2023-01-21T16:04:15Z","https://github.com/vuejs/vitepress/issues/434",0.70572525,{"description":2921,"labels":2922,"number":2926,"owner":2869,"repository":2870,"state":2871,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Describe the bug\r\n\r\nwhen I update the version to `\"vitepress\": \"^1.0.0-alpha.63\",` , and run `vitepress dev docs`, The Aside component is render nothing\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nupdate the vitepress version to `\"vitepress\": \"^1.0.0-alpha.63\",`\r\n\r\nrun `vitepress dev docs`\r\n\r\n`config.js`\r\n```\r\nimport { defineConfigWithTheme } from 'vitepress';\r\nimport vueJsx from '@vitejs/plugin-vue-jsx';\r\nimport baseConfig from '@vue/theme/config';\r\nimport { demoBlockPlugin } from 'vitepress-theme-demoblock';\r\nimport path from 'path';\r\n\r\nimport { i18n, nav, sidebar } from './themeConfig/index';\r\n\r\nexport default defineConfigWithTheme({\r\n extends: baseConfig,\r\n lang: 'zh-CN',\r\n title: 'SinoGear Vue',\r\n description: '',\r\n srcDir: './src',\r\n scrollOffset: 'header',\r\n ignoreDeadLinks: true,\r\n head: [['meta', { name: 'theme-color', content: '#3c8772' }]],\r\n themeConfig: {\r\n nav,\r\n sidebar,\r\n appearance: false, // 开启 light/dark 模式\r\n // Placeholder of the i18n config for @vuejs-translations.\r\n i18n,\r\n },\r\n\r\n markdown: {\r\n config(md) {\r\n md.use(demoBlockPlugin, {\r\n cssPreprocessor: 'less',\r\n scriptImports: [\r\n \"import * as AntDesignVue from 'ant-design-vue'\",\r\n ],\r\n scriptReplaces: [\r\n {\r\n searchValue: /import ({.*}) from 'ant-design-vue'/g,\r\n replaceValue: (s, s1) => `const ${s1} = AntDesignVue`\r\n },\r\n ]\r\n });\r\n }\r\n },\r\n\r\n vite: {\r\n server: {\r\n host: true,\r\n port: 3001,\r\n fs: {\r\n // for when developing with locally linked theme\r\n allow: ['../..']\r\n }\r\n },\r\n build: {\r\n chunkSizeWarningLimit: Infinity\r\n },\r\n json: {\r\n stringify: true\r\n },\r\n ssr: {\r\n noExternal: ['@wangeditor/editor', '@wangeditor/editor-for-vue', 'ant-design-vue', '@ant-design/icons-vue', '@babel/runtime']\r\n },\r\n plugins: [vueJsx()],\r\n css: {\r\n preprocessorOptions: {\r\n less: {\r\n javascriptEnabled: true\r\n }\r\n }\r\n }\r\n },\r\n\r\n vue: {\r\n reactivityTransform: path.resolve(__dirname, 'src')\r\n }\r\n});\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nrender aside component\r\n\r\n### System Info\r\n\r\n\r\n`packages.json`\r\n```shell\r\n\r\n\"@babel/plugin-syntax-jsx\": \"^7.18.6\",\r\n \"@vitejs/plugin-vue\": \"^4.0.0\",\r\n \"@vitejs/plugin-vue-jsx\": \"^3.0.0\",\r\n \"@vue/babel-plugin-jsx\": \"^1.1.1\",\r\n \"@vue/compiler-sfc\": \"^3.0.4\",\r\n \"conventional-changelog-cli\": \"^2.1.0\",\r\n \"cross-env\": \"^7.0.2\",\r\n \"del\": \"^6.0.0\",\r\n \"gulp\": \"^4.0.2\",\r\n \"gulp-babel\": \"^8.0.0\",\r\n \"highlight.js\": \"^10.4.1\",\r\n \"less\": \"^4.1.2\",\r\n \"lint-staged\": \"^13.0.3\",\r\n \"prettier\": \"^2.7.1\",\r\n \"rimraf\": \"^3.0.0\",\r\n \"transliteration\": \"^2.2.0\",\r\n \"vitepress\": \"^1.0.0-alpha.63\",\r\n \"vitepress-plugin-search\": \"^1.0.4-alpha.17\",\r\n \"vitepress-theme-demoblock\": \"^2.0.0\"\r\n```\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] 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.",[2923],{"name":2924,"color":2925},"need more info","bdbefc",2157,"The Aside component is render nothing","2023-04-05T00:04:02Z","https://github.com/vuejs/vitepress/issues/2157",0.70712906,{"description":2932,"labels":2933,"number":2938,"owner":2869,"repository":2870,"state":2871,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Describe the bug\r\n\r\nIt's unclear to me how these two differ, my understanding was that vitepress also calls vite build under the hood.\r\n\r\nHowever, I have a scenario where running `npm run docs:build` (`\"docs:build\": \"vitepress build`) results in\r\n\r\n```\r\n✓ building client + server bundles...\r\nbuild error:\r\nfile:///D:/git/some/path/docs/.vitepress/.temp/app.js:10\r\nimport { v5 } from \"uuid\";\r\n ^^\r\nSyntaxError: Named export 'v5' not found. The requested module 'uuid' is a CommonJS module, which may not support all module.exports as named exports.\r\nCommonJS modules can always be imported via the default export, for example using:\r\n\r\nimport pkg from 'uuid';\r\nconst { v5 } = pkg;\r\n\r\n at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)\r\n at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)\r\n```\r\n\r\nwhile running `npm run build` (`\"build\": \"vite build\"`) works perfectly fine.\r\n\r\nThese both use the same vite config (once in `vite.config.js` and once in the `vite:` property in vitepress' `config.js`, the latter with the `vite.config.js` deleted).\r\n\r\nThe module uuid (9.0.0) is not a CommonJS module, and building without vitepress works fine, so it looks like however `vitepress build` starts the build detects that incorrectly?\r\npackage.json of the uuid package: https://github.com/uuidjs/uuid/blob/4de23a6030e65ac72b3b015680f08e7e292681ed/package.json#L25\r\n\r\nTo be honest I'm not sure if this is a vitepress bug or even lower-level, at this point I'm mostly looking for guidance as to what vitepress build does different to vite build that could result in such differences.\r\n\r\nThanks!\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-qpoze8?file=package.json\r\n\r\nRun `npm run docs:build` if it doesn't run automatically.\r\n\r\npackage.json of the `postprocessing` package used for repro purposes here:\r\nhttps://github.com/pmndrs/postprocessing/blob/3e6ea9d8fddd2ca2d269e2182752f8199b8248af/package.json#L11\r\n\r\n### Expected behavior\r\n\r\nEither\r\n- Builds both work\r\nor\r\n- can understand the difference between the two better from the docs so I can resolve the issue myself\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz\r\n Memory: 31.89 GB / 63.85 GB\r\n Binaries:\r\n Node: 18.13.0 - D:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.13.2 - D:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.1\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.",[2934,2935],{"name":2866,"color":2867},{"name":2936,"color":2937},"stale","ededed",2421,"Different behaviour between `vite build` and `vitepress build` in same project","2023-09-02T00:04:09Z","https://github.com/vuejs/vitepress/issues/2421",0.7098777,{"description":2944,"labels":2945,"number":2946,"owner":2869,"repository":2870,"state":2871,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Describe the bug\r\n\r\nWhen I extract paths to a typescript enum in a single file and use it to define sidebar config, it is not work.\r\n\r\n### Reproduction\r\n\r\n1. define routes in `docs/.vitepress/routes.ts`\r\n\r\n```ts\r\n// typescript enum\r\nexport enum ROUTES {\r\n FOO = '/pages/foo/',\r\n}\r\n\r\n// or normal object\r\nexport const ROUTES = {\r\n FOO: '/pages/foo/,\r\n}\r\n```\r\n\r\n2. define sidebar in `docs/.vitepress/sidebar/index.ts`\r\n\r\n```ts\r\nimport { DefaultTheme } from 'vitepress'\r\n\r\nimport { ROUTES } from '../routes'\r\n\r\nimport { typeChallenges } from './type-challenges'\r\n\r\nexport const sidebar: DefaultTheme.Config['sidebar'] = {\r\n [ROUTES.FOO]: [\r\n {\r\n text: 'foo',\r\n items: [\r\n {\r\n text: 'foo-item',\r\n link: `${ROUTES.FOO}easy`,\r\n },\r\n ],\r\n },\r\n ],\r\n}\r\n```\r\n\r\n3. `docs/.vitepress/config.ts`\r\n\r\n```ts\r\nimport { defineConfig } from 'vitepress'\r\nimport { sidebar } from './theme/sidebar'\r\n\r\nexport default defineConfig({\r\n themeConfig: {\r\n sidebar,\r\n },\r\n})\r\n```\r\n\r\n\r\n### Expected behavior\r\n\r\nI want the dev server to run normally.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz\r\n Memory: 5.15 GB / 7.70 GB\r\n Container: Yes\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 - ~/.nvm/versions/node/v18.12.1/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.35 => 1.0.0-alpha.35\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nThe error info\r\n\r\n\r\n\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.",[],1768,"Cannot find package 'docs' imported from xxx/docs/.vitepress/config.ts.timestamp-1672993082912.mjs","2023-01-21T14:16:49Z","https://github.com/vuejs/vitepress/issues/1768",0.71094555,{"description":2952,"labels":2953,"number":2955,"owner":2869,"repository":2870,"state":2871,"title":2956,"updated_at":2957,"url":2958,"score":2959},"\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\nAfter running npx vitepress, I open the browser and load the address of http://localhost:3000, but I get a error.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\nPS D:\\桌面\\demo> npx vitepress\r\nvitepress v0.5.0\r\nvite v1.0.0-rc.4\r\nlistening at http://localhost:3000\r\n[vite] Failed to resolve module import \"vue/dist/vue.runtime.esm-bundler.js.0.0-rc.5@vuedist\u000bue.runtime.esm-bundler.js\". (imported by /@app/components/Debug.vue)\r\n\r\n**Expected behavior**\r\nGetting \"Hello Vitepress\" in browser.\r\n\r\n**System Info**\r\n- vitepress version: v0.5.0\r\n- vite version: v1.0.0-rc.4\r\n- Node version: 12.14.0\r\n- OS version:10.0.19041 暂缺 Build 19041\r\n\r\n**Additional context**\r\n尤大大,I am you big fan.\r\n",[2954],{"name":2866,"color":2867},65,"服务启动之后,进入地址报错","2023-01-21T16:25:36Z","https://github.com/vuejs/vitepress/issues/65",0.7129881,{"description":2961,"labels":2962,"number":2964,"owner":2869,"repository":2870,"state":2871,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\r\n\r\nI wrote a custom VitePress theme with UnoCSS, and I tried to import the theme from another project.\r\n\r\nBut after imported, the dev server failed to render the page and reported \r\n\r\n```\r\n[plugin:vite:import-analysis] Failed to resolve import \"virtual:uno.css\" from \"../theme/.vitepress/theme/index.js\". Does the file exist?\r\n/home/projects/stackblitz-starters-9izmbf/theme/.vitepress/theme/index.js:3:9\r\n1 | // https://vitepress.dev/guide/custom-theme\r\n2 | import Layout from './Layout.vue';\r\n3 | import 'virtual:uno.css';\r\n | ^\r\n4 | \r\n5 | export default {\r\n```\r\n\r\nI'm not sure which part of it is wrong. I don't even know if this is a VitePress bug. Please check the Stackblitz repro below.\r\n\r\n### Reproduction\r\n\r\nThis StackBlitz project reproduces the bug. BTW, the start script might execute very slowly.\r\n\r\nhttps://stackblitz.com/edit/stackblitz-starters-9izmbf?file=readme.md\r\n\r\n### Expected behavior\r\n\r\nThe test project in the above StackBlitz repro with external theme to work normally without additional configuration.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 16.20.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.2 - /usr/local/bin/npm\r\n pnpm: 8.6.10 - /usr/local/bin/pnpm\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.",[2963],{"name":2866,"color":2867},2845,"Cannot use external theme with UnoCSS","2023-09-01T00:04:32Z","https://github.com/vuejs/vitepress/issues/2845",0.71464974,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foZpsIgGkI4iRkzAuV4qXLVArKsrwEjqbjeSZ9K-xwFE":-1},"/vuejs/vitepress/2587"]