In the vein of #7, I think optimize-js also doesn't work optimally for Browserify.
Whereas Webpack wraps modules in function expressions that are elements in an array, Browserify wraps modules in function expressions that are elements in an array which is in turn a value in an object with numeric keys, something like this:
!function(o){
/* loader code */
}({
1:[function(o,r){/*module 1 code */}, {}],
2:[function(o,r){/*module 2 code */}, {}],
3:[function(o,r){/*module 3 code */}, {}]
}
I noticed in making my patch for #7 and testing on The Cost of Small Modules benchmark repo that optimize-js had essentially no effect on the Browserify bundles, and I'm pretty sure this is why.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4