You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to the contributors of this plugin, it solves many pain points of eslint-loader.
We are using webpack to output different type of bundle through multi-compiler. If setting threads of eslint-webpack-plugin, the output will be incomplete. So it's not recommended to use this option with webpack multi-compiler?
Or it can be fixed in webpack? The result of webpack@4 and webpack@5 is similar.
[webpack-cli] Compilation finished
✨ Done in 2.93s.
Some of our project's tests are based on the output of webpack. So the incomplete console output let the tests fail after bumping the version of eslint-webpack-plugin to 2.4.1.
Thanks to the contributors of this plugin, it solves many pain points of
eslint-loader
.We are using webpack to output different type of bundle through multi-compiler. If setting threads of
eslint-webpack-plugin
, the output will be incomplete. So it's not recommended to use this option with webpack multi-compiler?Or it can be fixed in webpack? The result of webpack@4 and webpack@5 is similar.
Expected Behavior
bundle output should be
Actual Behavior
bundle output is incomplete
[email protected] and [email protected] with threads
bundle output: incomplete
console output
Some of our project's tests are based on the output of webpack. So the incomplete console output let the tests fail after bumping the version of
eslint-webpack-plugin
to 2.4.1.[email protected] and [email protected] with threads
bundle output: High probability incomplete, Small probability complete(according to the test of reproducible repo)
console output
How Do We Reproduce?
Reproducible repo
The text was updated successfully, but these errors were encountered: