It might worth reconsidering the polyfilling issue.
Originally I shipped all necessary polyfills to make it easier to adapt the library, but that comes with some cons:
- Shipping the polyfill adds extra weight to the lib
- If the polyfill is applied automatically, then that could be applied before the app developer applies its own polyfill => this could result in hard to debug situations, where this lib would polyfill something sooner than the app developer.
Using something like polyfill.io, or just a separate polyfill js file made by the app author should be an easy enough thing to do, since I'm already assuming a lot of knowledge with these modules anyway.
Anyway, needs some more research into polyfilling best practices.
It might worth reconsidering the polyfilling issue.
Originally I shipped all necessary polyfills to make it easier to adapt the library, but that comes with some cons:
Using something like polyfill.io, or just a separate polyfill js file made by the app author should be an easy enough thing to do, since I'm already assuming a lot of knowledge with these modules anyway.
Anyway, needs some more research into polyfilling best practices.