allegro / allegro/typescript-strict-plugin

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

Open
#54 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
397
Forks
34
PR merge metrics
PR metrics pending

Description

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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.