Closed jaydenseric closed 7 years ago
This package breaks in IE 11 due to it's unpolyfilled use of Object.assign.
Object.assign
It is risky to rely on Next.js to apply a global polyfill, because its not guaranteed - in v3 latest it is not present:
This issue can be resolved by refactoring all usage of Object.assign to spread operator syntax. It's more elegant that way anyway.
This is now fixed with new babel presets.
This package breaks in IE 11 due to it's unpolyfilled use of
Object.assign
.It is risky to rely on Next.js to apply a global polyfill, because its not guaranteed - in v3 latest it is not present:
This issue can be resolved by refactoring all usage of
Object.assign
to spread operator syntax. It's more elegant that way anyway.