Could you use a similar logic like in module.loaders?

A test, include and exclude option, which could be a string, RegExp or array of those.

(defaults to test: /\.js($|\?)/i)

http://webpack.github.io/docs/configuration.html#module-loaders
https://github.com/webpack/core/blob/master/lib/LoadersList.js#L69-L77

Great idea @sokra, I've updated the PR. Long term this logic could be extracted and held separate in a filtering module to keep the code DRY.

I might be mistaken, but I don't think this code does what this pull-request intended.

Right now it runs the regexp matches as a filter against "files" which is an array of the generated chunks. Shouldn't it run it against the individual required modules? I'm not sure what use there is in telling it to exclude uglifying a whole generated chunk, especially since webpack is usually just generating one chunk.

@snapwich sorry for not being clear enough in the PR description. You're right, the change here affects the whole bundle. My use case is that one of the bundles contains a legacy JS file that should not be minified and I want to prevent that file form being uglified. It would be better to exclude just a single file instead of whole chunk but I haven't found a way to do that with the webpack plugin system.

I've just created a tiny loader for this https://github.com/bestander/uglify-loader
It does not expose uglify API yet and calls uglify-js with default parameters.