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

allegro / typescript-strict-plugin

Typescript plugin that allows turning on strict mode in specific files or directories.

MIT License

332 stars 29 forks source link

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

Open ajw170 opened 1 year ago

ajw170 commented 1 year ago

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 commented 1 year ago

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

kamkry commented 1 year ago

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?