Webpack runtime doesn’t work on Safari 5

Do you want to request a feature or report a bug?

Report a bug.

What is the current behavior?

The current webpack v4 runtime uses Function.prototype.bind which is not available in Safari 5.


If the current behavior is a bug, please provide the steps to reproduce.

Just try to run any bundle built by webpack v4 in a Safari 5/Webkit ~534.

What is the expected behavior?

The runtime code should work on old Webkit versions.

I can manually insert a bind polyfill in my template before the bundles, but I’d really like to avoid doing this manually. I’ve tried to insert the polyfill inside the runtime, but as you can guess it, the runtime is executed before the polyfill.

If this is a feature request, what is motivation or use case for changing the behavior?

I know Function.prototype.bind is essential and that Safari 5 is an old browser, but since I didn’t find any general “browser support” for webpack, the runtime should work on old Webkit versions.

Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.

Webpack version: 4.5.0
Node: 9.8.0

Author: Fantashit

3 thoughts on “Webpack runtime doesn’t work on Safari 5

Comments are closed.