I’m working on a small application, consisting of 3 services each under 100 Typescript files. I’m using tsc-watch to automatically restart these services, which runs tsc --watch under the hood.

When I run the application normally on the compiled files they are completely idle until a HTTP request comes in, but with tsc --watch they each take ~5% CPU time, even if nothing is changing.

This seems high, because I was under the impression that tsc --watch just listens for some OS level event that a file has changed, so I’m wondering if that fails for some reason and perhaps it’s falling back on polling and checking every file for changes.

I’m not certain how I can begin to debug this!