webpack/lib/optimize
Kenny Tran 7edffc381d Small refactor for getting size
Currently, map is being called to extract sizes then reduce is called on that; so 2 iterations through the array. It is possible to solve this with only reduce: 1 iteration. reallyUsedModules probably won't ever be big enough for this to matter, so it comes down to readability.

I think doing a once-and-done reduce could be an improvement here. What do you guys think?
2015-05-21 12:39:08 -07:00
..
AggressiveMergingPlugin.js added linting 2015-04-23 23:55:50 +02:00
CommonsChunkPlugin.js Small refactor for getting size 2015-05-21 12:39:08 -07:00
DedupePlugin.js added linting 2015-04-23 23:55:50 +02:00
FlagIncludedChunksPlugin.js improved chunk loading 2013-02-24 02:05:55 +01:00
LimitChunkCountPlugin.js added linting 2015-04-23 23:55:50 +02:00
MergeDuplicateChunksPlugin.js fixed bug where duplicates are not detected 2014-02-15 11:29:15 +01:00
MinChunkSizePlugin.js added linting 2015-04-23 23:55:50 +02:00
OccurenceOrderPlugin.js fixed #179 typo in OccurenceOrderPlugin 2014-02-25 08:51:40 +01:00
OccurrenceOrderPlugin.js added linting 2015-04-23 23:55:50 +02:00
RemoveEmptyChunksPlugin.js apply optimizing on extracted chunks too 2014-09-23 08:42:54 +02:00
RemoveParentModulesPlugin.js apply optimizing on extracted chunks too 2014-09-23 08:42:54 +02:00
UglifyJsPlugin.js added linting 2015-04-23 23:55:50 +02:00