Supporting custom webpack.config.js about size-limit HOT 10 CLOSED

Sure. Let's do it. Do you want to make PR?

Also, why custom config should not include compression and minification plugins? What if users will want to customize them too?

from size-limit.

Totally possible. I was assuming that the Compression and Uglify plugins the webpack config in index.js uses were intentional. e.g. what would happen if one attempted to use require('webpack').optimize.UglifyJsPlugin instead of require('uglifyjs-webpack-plugin')?

from size-limit.

uglifyjs-webpack-plugin loads latest beta with ES6 support

from size-limit.

Got it. What I'm trying to figure out is the best way to (or if it's feasible) to implement the following:

• Is it possible to determine if an arbitrary webpack config object, config, needs modification by size-limit?

In other words: what's an efficient way to check if config.plugins has both a compatible minifier plugin and a compatible compression plugin?

from size-limit.

I think we could ignore this problem. If you pass custom config, it is your responsibility now.

If we will have a lot of issues, we can add check later.

from size-limit.

That's reasonable. Will take a stab at this in the next couple of weeks.

from size-limit.

@indexzero @ai I have submitted #29, and #31 to enable a --config flag that supports a custom webpack config.

from size-limit.

Released in 0.12

from size-limit.

@SivanMehta I'm wondering, how are you using this --config option? How do you handle the files option?

from size-limit.

This PR should have supported the usage as described in the initial issue descriptions

size-limit --config ./my-custom-webpack.config.js

from size-limit.