You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
When I am not touching any files in my project, TSC with watch: true configured will not consume much (if any) CPU.
Actual behavior:
When I am not touching any files in my project, TSC with watch: true configured consumes a notable amount of CPU on my laptop, enough to keep the fan on consistently.
With polling enabled, tsc -w -p takes up 10-15% CPU on our project files.
With polling disabled, the same command uses virtually no CPU if no files are changing.
TypeScript Version: 2.4.2
Expected behavior:
When I am not touching any files in my project, TSC with
watch: true
configured will not consume much (if any) CPU.Actual behavior:
When I am not touching any files in my project, TSC with
watch: true
configured consumes a notable amount of CPU on my laptop, enough to keep the fan on consistently.This blog post suggests that the culprit is a recent change to polling for changes.
Notes:
I am using VSCode with the built-in TypeScript support, the default TypeScript build task and a tsconfig.json like:
The text was updated successfully, but these errors were encountered: