-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Can not load "webpack" #1497
Comments
|
Thanks for the report, I will look into it as soon as I can |
Can you please check if this is still an issue in |
@dignifiedquire yep, still seeing it with v0.13.1 |
I'm also still having the same issue. My project tried to closely follow this example project.
My
|
same here :( Node v0.12.7 Same Example tried.
|
To get around this issue downgrading karma. This set up works: "karma": "^0.12.36",
"karma-chrome-launcher": "^0.2.0",
"karma-html-reporter": "^0.2.6",
"karma-jasmine": "^0.3.6",
"karma-phantomjs-launcher": "^0.2.0",
"karma-webpack": "^1.6.0", |
Another working config: "karma": "^0.12.36",
"karma-chrome-launcher": "^0.2.0",
"karma-cli": "^0.1.0",
"karma-mocha": "^0.2.0",
"karma-sourcemap-loader": "^0.3.5",
"karma-webpack": "^1.6.0", |
Just a quick update, I was able to find out what the underlying issue is: In short dependency injection sucks. Fix coming soon |
Okay I've just released |
now just have to wait till that PR gets merged... ಠ_ಠ |
Hooray for OSS! Also, thanks for the quick attention to the problem - pretty awesome turnaround time. |
OT: DI sucks because it exposes cyclic dependencies? I'd say that's a win for DI and by avoiding partial/unreliable initialisation ;) Happy for fix, would be great to get codymikol/karma-webpack#63 merged and released =)
|
@dignifiedquire closed? |
yep fixed now |
Updating the karma version allows the tests to run. Was related to karma-runner/karma#1497
https://stackoverflow.com/questions/31444743/karma-cant-load-webpack/31452564
Its reproducible when you install all the latest versions of karma-* on node v2.3.4
The text was updated successfully, but these errors were encountered: