Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
ajw170 opened this issue May 2, 2023 · 2 comments
Open

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

ajw170 opened this issue May 2, 2023 · 2 comments

Comments

@ajw170
Copy link

ajw170 commented May 2, 2023

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
Copy link
Author

ajw170 commented May 2, 2023

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

@kamkry
Copy link
Collaborator

kamkry commented Sep 4, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ajw170 @kamkry