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
--extendedDiagnostics and --generateTrace do not work #1375
Comments
Hi @blake-newman, thanks for your shares and the fair worded :). I can't reproduce this problem in https://github.com/johnsoncodehk/volar-starter but I try to fix, it do not release yet but you can try it in local env by following steps:
If it still not working please provide repro case so I can check the difference. |
@johnsoncodehk thank you for the quick fix. This has fixed
We have some bank holdays over next couple of days in UK so will action inviting you to repository if I'm unable to triage and resolve myself. |
So from what i can tell the issue is due to the following: There are many outputs in The diagnostics and information is captured in I'm not sure what is causing the above; but that is the reason its failing. |
I can reproduce |
Proxy tracing API to `tsserverlibrary` fixes: vuejs#1375
@johnsoncodehk i believe i found a way to enable this feature; not sure is the solution is appropriate but PR'd it anyway |
Thanks for investigating it! |
Since v0.35.0 auto-import cache is not support for TS <= 4.6.x, and it's re-support in v0.37.1, it may resolve the performance issue on your project. |
The following tooling is useful for diagnosing TypeScript performance issues in applications.
Reports of slow IDE experiences may not be directly due to Volar but underlying poor preforming hot code in applications. In our case we have a very large project and have always suffered performance issues. Volar doesn't seem to respond well; likely due to it now generating more typing for vue files.
I don't want to create yet another issue about bad performance with Volar; because it may not be due to Volar itself but underlying poor performance in application code.
The ability to use this tooling will help users (and ourselves) be able to triage performance issues before blaming the tooling; however the methods to triage performance issues do not work.
I've taken a look myself into why
vue-tsc
is not reporting on diagnostics; but i've not yet found any resolutions as to why this may be.Extended Diagnostics
As you can see with
vue-tsc
the extended diagnostics is reporting more files checked (which makes sense as this would be the vue files), but the types and instantiations are basically no longer being reported.Trace Generation
This error appears because the trace information is empty; which is not expected. Which indicates tracing and diagnostic information is bailing out.
Removing the generated code for VLS, which causes diagnostic errors (we use TSX and vue 2 so it isn't required to be generated in our scenario). These errors are filtered out but I was curious if that caused bail out of counting and tracing type information. After removing all diagnostic errors from generated code it still fails; so this tells me that the issue is not directly related to the generated code.
The text was updated successfully, but these errors were encountered: