Version 1.0.0

• Instead of wrapping the whole chunk into the check for polyfills, only wrap the entry modules. This avoids conflicts with other plugins and ensures that our generated code will be considered for calculating the chunk hashes.
• Breaking: Use a special loader to wrap entry modules. It is a bit less magic than before and allows for different configurations per entry-chunk. This is a breaking change and requires a new configuration scheme, please see the updated readme file for details.
• Generate polyfill files for all possible combinations. If you configure to use [A, B, C], then we generate files A, B, C, AB, AC, BC, ABC. The browser requests the file that contains all necessary polyfills. This saves bandwidth, as no unnecessary polfills are loaded. Since all files are contained in the bundle, they can be served by a very dumb webserver (instead of something like polyfill-service).
• Breaking: Support for loading the polyfills from cdn.polyfill.io was dropped because we now include these optimized files statically in the bundle such that any dumb webserver can serve the optimal polyfill combination for each client.