-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Verbose Build option to be able to track down errors #422
Comments
FYI. After debugging, I found the reason was an undefined component name in a markdown file. Now, the undefined component name has been deleted. However, it would be great if we could figure out a better error message for this kind of case.
|
EDIT: Following answer is not applicable. The commit was reverted, but we will reintroduce it. It needs some changes in core. Few updates on this. Vue no longer throws that error during SSR if the component is not registered. So, the builds will succeed fine, however on viewing the site there will be hydration mismatches. So, from next version, one will be able to run ![]() |
Is your feature request related to a problem? Please describe.
I'm getting an opaque build error when trying to build a vitepress site which works without issue during dev (i.e. npm run docs:dev) but fails during build.
I would like extra info during the build, like which page or component failed to renderer so there's some hope in being able to track it down.
Describe the solution you'd like
Ideally the extra info of what Page and Component failed to render would be included in the error message by default, alternatively being able to run the build with verbose build output, e.g:
Describe alternatives you've considered
Couldn't find a way to generate verbose build output, e.g:
I wasn't able to find what the supported switches for the build command are, it would be nice if the available command options was available in the standard help options, e.g:
$ vitepress build -h $ vitepress build --help $ vitepress build ?
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: