Closed eddyw closed 3 years ago
Can you add tests for these use cases?
@eddyw @blacksonic Any updates on this? Really needed feature 😬
@bricss it's been quite some time since I opened the PR. Currently I'm no longer using tslint-loader and I have little time to be able to implement the tests. If anybody is willing to help with that, it'd be cool.
Anyway, I will see if I can make some time this month to implement the tests.
Any updates? It would be a really convenient addition.
@adanski I haven't had time to continue with this. Sorry, I've even forgotten about it. I've switched from Webpack to using FuseBox bundler because it has first class TS support which seemed more suitable for my projects.
The changes were small and only tests are missing if anybody is interested in taking over.
Everyone who needs proper TS linting without artefacts, try to use https://github.com/Realytics/fork-ts-checker-webpack-plugin
It's related to #74 and #85 The idea is to allow users to customize options on
failOnHint
to take into account the severity of the rules. For instance, rules whose severity iswarning
shouldn't break the build process. For instance:This PR allows
failOnHint
property to be an object that accepts these optional properties:When
ignoreWarnings
is set to true, when there are only warnings, they are ignored and the compilation succeeds. However, if there is at least one error, both errors and warnings are shown and the compilation fails (this way doesn't break existing configuration)When
displayWarnings
is set to true, compilation succeeds but warnings are shown (webpackInstance.emitWarning
)silent
doesn't throw an error only displays error output (webpackInstance.emitError
). It's useful together withemitErrors: true
andwebpack.NoEmitOnErrorsPlugin
webpack plugin. We can get a nice and clean output by combining these, specially with the plugin.