Allow using config folder other than .vitepress

[Pandapip1]

Is your feature request related to a problem? Please describe.

The naming .vitepress seems to imply some sort of configuration. However, in some instances, the configuration is a major enough part of the project that it deserves to be in a subfolder of the src directory. Basically, instead of .vitepress and src, I would like to be able to use src/vitepress and src/website.

Describe the solution you'd like

I'm not entirely sure how vitepress could determine the path. Maybe a vitepress build CLI option?

Describe alternatives you've considered

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the docs.
• Read the Contributing Guidelines.
• Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.

[maxpatiiuk]

HI, @brc-dd. This issue was labeled as has-workaround, but I do not see what workaround is available. Could you please clarify?

---

It appears that VitePress is hardcoded to look for the .vitepress directory, with no CLI option to customize that:

vitepress/src/node/config.ts

Lines 28 to 29 in 3eb4374

	const resolve = (root: string, file: string) =>
	normalizePath(path.resolve(root, `.vitepress`, file))

I wish to customize the directory name because TypeScript is hardcoded to ignore directories that start with ., even if explicitly included in tsconfig.json. That means files in the .vitepress directory are not covered by our TypeScript config.

Worse still, typescript-eslint throws an error if you try to lint a file that is not covered by TypeScript, so we are forced to also disabled ESLint for .vitepress directory.

[brc-dd]

The workaround was basically you can store the files wherever you want. Just reexport default from config/theme.

And regarding ts, you can definitely include files in directories starting with dot, it just won't expand them in **. So you need to write docs/.vitepress/**/*.ts or something (but even then you should use it in composite mode with separate tsconfig for config and theme/vue/md, your aliases and stuff won't take effect inside config files).