Seperate presets for maximum compatibility and convenience

[Richienb]

One preset will be as if webpack never removed the feature, and another preset (the new default) will remove all the polyfills that have no practical purpose (#44. #20), setting mostly everything else that is yet to be polyfilled as no-ops (#41). - biggest change is noticable for the globals.

[Richienb]

@afonsojramos thoughts?

[afonsojramos]

I'm going to suggest a different approach. What do you think of accepting an argument that defines which modules should not be polyfilled? I suppose that most people want as much as they can, and, if they don't want them, they can just disable them manually.

[Richienb]

What do you think of accepting an argument that defines which modules should not be polyfilled?

This is already an option called excludeAliases.

I suppose that most people want as much as they can, and, if they don't want them, they can just disable them manually.

I don't think so. People in the past have gotten confused by what they thought were polyfills which actually turned out to be shims. So, I want to make it obvious what isn't supported.

[afonsojramos]

However, this package doesn't even have fs fallback, so setting it as false definitely helps and enhances the usability of this package. Please reconsider #45. People request it for a reason.