I'm not sure type checking should be enabled while this is still an issue:wbuchwalter/tslint-loader#76. Even on small projects I noticed a performance hit of 250-300%.

@gsteacy agreed, I've stopped usingtslint-loader and switched totslint-webpack-plugin because of this.

@pelotom are you able to do that without ejecting though?

@stevenmusumeche no.

As this issue hasn't been updated for a while, I am going to close it. If there are any updates feel free to re-open and comment. 👍

FYI:fork-ts-checker-webpack-plugin, which was added in 2.10, supports linting rules that require type checking by sharingts.Program instances, so that feature should be available anyway.

Yes, however be aware thatfork-ts-checker-webpack-plugin hasa bug with theno-unused-variable rule which may or may not bite you. For my project it was intolerable; I had to disable the rule and use thetsc—noUnusedLocals flag instead.

That's currently the case in the template -noUnusedLocals is used as a compiler option,no-unused-variable is not part of the linter config.