Evaluate hard-source Webpack plugin

[KyleAMathews]

https://github.com/mzgoddard/hard-source-webpack-plugin

Still early but very promising. Caches intermediate build steps. Can dramatically speed up incremental builds both for dev and prod.

[thangngoc89]

Phenomic implemented it here MoOx/phenomic#646

[zhaoshengjun]

Just curious: What's the difference between hard-source-plugin and DllPlugin?

ps: here's some articles related to DLLPlugin in case you don't know:

https://robertknight.github.io/posts/webpack-dll-plugins/
https://medium.com/@soederpop/webpack-plugins-been-we-been-keepin-on-the-dll-cdfdd6cb8cd7#.d1g27iray
http://engineering.invisionapp.com/post/optimizing-webpack/

[KyleAMathews]

@zhaoshengjun the DLLPlugin speeds up Webpack by making it do less work as you tell it to not pay attention to a list of modules. hard-source-plugin speeds up Webpack by caching incremental work so again Webpack does less but this time by avoiding repeating work that's already been done.

[gaearon]

How do we know when/if it becomes stable? I don’t understand how to evaluate it.

[KyleAMathews]

I haven't tried it yet myself so can't comment on its stability but the first thing to do I'd think is try adding it to a create-react-app and see the performance difference to see if that's significant enough to worry about making the change.

I'll be trying it in Gatsby soon. From @thangngoc89 and @MoOx's experiments in Phenomic, it seems quite usable.

[MoOx]

Fun you mention us, we just released yesterday a new Phenomic release, which makes available the new "cache" option based on this plugin, that works for both webpack 1 & 2.

Here are some number in a picture

[gaearon]

@MoOx Would you like to submit a PR to CRA enabling it?

[gaearon]

Hmm, I don’t think it’s mature enough. We shouldn’t leave people with issues like mzgoddard/hard-source-webpack-plugin#31 after ejecting. Let’s wait more.

[MoOx]

I was about to tell you this :)

I opened mzgoddard/hard-source-webpack-plugin#40 so we can track "maturity" :)

[gaearon]

To be fair, regardless of the version number, I won’t feel good using this until major issues are solved. We are also conservative about updates and lock package versions so that CRA itself is less fragile when possible.

[MoOx]

I totally understand and I don't think "just bumping" will magically make this "mature".
I think changing the version number won't be done until current major issues are solved, even if I didn't explicitly talk about that ^^.

[shrynx]

Consider using happypack as an alternate?
it has caching and does threading too. I have implemented both happy loader(for build process) and webpack hard source(for dev process) in my fork. the speed gains are really good.

[wtgtybhertgeghgtwtg]

happypack doesn't work with webpack@2.0.0 and has issues with Windows.

[gaearon]

Closing, as both suggestions appear to be flaky for some users.
I don't think this is a promising direction unless Webpack core officially embraces it.
(I do think, however, that aggressive caching is essential, and Webpack could do better there.)

cc @sokra @TheLarkInn

[sokra]

Sure vote for it: https://webpack.js.org/vote/

[thangngoc89]

@sokra spent 30 influences for it