Feature Request: Show all errors and warnings in project for all JavaScript and TypeScript files, not just opened ones

[kevinjreece]

I am using VS Code on a project at work that has hundreds of files and many layers of nested sub-directories. I frequently make changes that break many files, such as changing the call signature of a commonly used method. Since the project is entirely typescript, it is useful to be able to open the "Problems" view and see the errors and warnings my change caused in the files I have open. However, because of the size of the project, I still need to go to my terminal and run our own make commands to see the list of problems. I then need to perform the fun dance between my terminal and VS Code, searching for the right line in the right file before I can fix the problem.

What I need is a way to tell the "Problems" view to show me all errors and warnings across all open and closed files in my project. This would allow me to see all problems in a single list and quickly click through and fix them.

[dbaeumer]

@waderyan this is a feature request for the builder work we discussed with the TS team.

[waderyan]

For reference here is a link to the issue - microsoft/TypeScript#11229

[plievone]

Well, I just use a watching build task with "problemMatcher": "$tsc-watch" (see https://code.visualstudio.com/Docs/editor/tasks#_processing-task-output-with-problem-matchers) and all errors and warnings are properly shown in the Problems view. It is quite a nice workflow because changes in open files are noticed immediately due to language server, but save triggers incremental compilation (with tsc --watch) which still takes a while, but I can control that latency by saving/not saving yet.

[maxime1992]

any ETA on this ? There's a lot of issues opened for that feature and not sure if I missed anything or not 😄

[waderyan]

@maxime1992 thanks for the follow up. This is on our radar. No firm timeline yet.