-
-
Notifications
You must be signed in to change notification settings - Fork 121
Conversation
Looks good. I guess @gaearon will be happy about this? Can you fix the tests? Looks like an eslint issue is here :) (Will add prettier soon to avoid this) |
d2e999d
to
7caa2c4
Compare
Not sure how that squeaked by. Made a few modifications. All tests now passing. |
I take that back. A few older versions of node/webpack appear to have issues. I'll look into it. |
Is webpack@1 support important? Is there any possibility of a new major version that supports webpack@2 only? I'll be honest, I'm not certain how much time I want to invest int getting webpack@1 tests passing. * I will definitely get webpack@2 tests passing in node 4 |
7caa2c4
to
d0ab787
Compare
Update: All webpack@2 tests passing |
webpack 1 support is important yes, and probably not hard to do (I recently tweaked the tests but your rollbacked this) |
d0ab787
to
c5b3078
Compare
Honestly not a huge fan of the solution but I think it is the best we are going to do. Internally webpack@2 has changed and requires errors to be passed through So the solution, conditionally send as an ESLintError: All tests now passing. |
Awesome. Thanks for the quick publish 👍 |
Minimizes duplicate output in the following situations.
Duplicate ESLint messages are logged due to Webpack throwing
NonErrorEmittedError: (Emitted value instead of an instance of Error)
. This is done by emitting an new Error type ESLintError.Duplicate ESLint messages caused by both emitting, and throwing an error. This was fixed fairly easy by moving the emit to below the throws.
Note: Because the formatted message acts as a stack trace, our ESLINTError sets the stack to the message. This keeps output clean when logged.
A few before and after screenshots:
Build Before Patch
Build After Patch
Start Before Patch
Start After Patch