-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ModuleNotFoundError not being handled #214
Comments
Any opinions / thoughts on this? |
@d3viant0ne any thoughts here? this would be super helpful to get merged as existing error messages are cryptic and misleading. |
There was a bit of discussion on how to fix this without breaking things for the angular/cli users, that particular integration is no longer an issue. I'm in the middle of rewriting karma-webpack to close out some of the long standing features, i'll get a quick fix in to deal with the error messages in the current major this weekend. |
I can't get proper error messages with or without
|
BEFORE YOU SUBMIT please read the following:
I'm submitting a bug report
Webpack version:
2.2.0
Webpack Karma version:
2.0.1
Karma version:
1.4
Please tell us about your environment:
OSX 10.x
Browser: [Phantom 2.1.1]
Current behavior:
If a misspelled module is imported in a test the following stacktrace is emitted:
Expected/desired behavior:
Something similar to this, and not having to restart the test runner would be great!
Currently our setup has
bail: true
and this doesn't give me my expected result but at least this error message is much better.it seems that the
callback
being called here mostly for success cases:https://github.com/webpack-contrib/karma-webpack/blob/v2/src/karma-webpack.js#L167
needs to be called with an
err
.The text was updated successfully, but these errors were encountered: