-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Webpack4 #7387
Webpack4 #7387
Conversation
…as they caused multiple issues on linux
(builds on and replaces #6620) |
actually, it's not olm slowing down karma (removing it from webpack entirely only speeds things up by a few seconds). It's the 28MB of all-tests.js which is presumably bogging it down. |
(it's roughly 2x as slow as on webpack 2 :|) |
(and this is with |
so karma-webpack 3.0.5 is 4x slower than 4.0.0-beta.0 for webpacking for unknown reasons. However, 4.0.0-rc.1 and 4.0.0-rc.2 fail with a different error. So: pinned for now
n.b. 4.0.0-rc.[12] are broken due to codymikol/karma-webpack#363 |
@ara4n this does work on Windows, and it feels faster than webpack 2 for me. Might be a slight difference in hardware though. |
LGTM'd irl from dave |
Thanks for indirectly merging my few commits :) Awesome to see this merged |
thank you for doing all the hard work. i'm so sorry it took so long to merge :( |
Update @MTRNord's Webpack4 for latest libs. Had to downgrade karma-webpack from 4.0.0-rc2 to 3.0.5 due to bugs in handling paths.
It works well on my Mac with node 10.9.0 (and npm 6.4.1), but
npm run test
spends 58s in webpack from karma, probably re-packing Olm (even though webpack.config.js tells it not to). I'm going to ignore this given we're about to switch to WASM.@turt2live does this work on Windows? (karma-webpack 4 apparently is broken on Windows, hence also downgrading it here)