Open bruceauyeung opened 4 years ago
"no type errors" refers to errors with typescript types, not lint errors or warnings from eslint.
So the error message is technically correct: typescript found no type errors. Your build failed because of a linter error.
But I agree that the diference is subtle and might be missed.
I'm not sure if and how we can change this output from fork-ts-checker-webpack-plugin, though ...
Version
3.12.1
Reproduction link
http://no.reproduction.repo
Environment info
Steps to reproduce
the very last 3 lines :
No type errors found
, but actuallyeslint-loader
reports:'NetExtra' is already defined (no-redeclare) at src\commons\node\netExtra.ts:26:18:
this situation may mislead developers , especially there are lots of warnings.
if this is because different tools report them, can we have a summary report ?
What is expected?
if any stage of building failed, the final report will report failure
What is actually happening?
the final report says
No type errors found
wheneslint-loader
reporting an error