Making sure that loading it with webpack resolves to non-polyfill whe…

[activenode]

…n native support

Loading it with webpack would require additional checkings which are actually not required if we just return global.Intl as it is set to Polyfill anyway when no native support is given.

[activenode]

Are you really sure that the given test is correct? Why should the Polyfill according to the Specs deliver something else than the Spec given one?

[activenode]

@andyearnshaw Can you please check this commit?

[caridy]

This is a non-backward compatible change, but it might be fine for the next release. The reasoning here is how someone will get a handle on the polyfill if they want to, even if the env supports Intl? they can still do it by setting Intl to undefined, importing this, and grabbing the new global. Maybe we can just offer another file that can be required, to get the inner pieces. Will merge it before next release.