New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(config): add themeDir
option
#3291
base: main
Are you sure you want to change the base?
Conversation
Would it be better to include this as a command line argument? e.g. In this way you can even specify a directory outside docs: |
@zhangyx1998 for export default defineConfig({
srcDir: '../'
}); In this PR my target is to be able to configure the theme entry file, which is not currently configurable and is always resolved from |
Not really. I meant the alternative path to This option is impossible to live inside user config because it tells vitepress from where it should load user config. Currently vitepress always assumes user config entry to be Providing an option to override it seems like a once-and-for-all solution. |
It's just some random thought, please feel free to discard it. |
That might be a good option, there are already option to configure the |
Together with #3290 I want to achieve project structure like the following:
The main motivation: working with private folder (
.vitepress
) cause a-lot of issues with TypeScript and eslint (like motioned in #1047), even when you get the typechecker and the linter to work with.vitepress
, the code editor (VSCode) fails to evaluate the the files correctly.Also, the above structure is more familiar to Vite, I hope it would be the default for VitePress