Why is an error returned (exit code 1) just because no strict files were found?

[ajw170]

Title pretty much sums it up. Was just wondering why an error would be returned in the event that no files match the strict criteria. This may be desired behavior; for instance, I intentionally set the "paths" array such that no files would be checked. In this case I'd expect the build script to continue successfully when using "npm run build tsc-strict && other-script"; instead it fails.

[ajw170]

Would be happy to create a PR to address this, unless this was intended behavior.

[kamkry]

I'm trying to understand using the script if the paths array is empty and there are no //@ts-strict comments. Could you tell me more about your use case?