-
Notifications
You must be signed in to change notification settings - Fork 135
Do you need to polyfill promises? #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, the library expects an implementation or a polyfill. If you use async iterators, you'll need |
Okay good to know! It'd be great to either document that somewhere or even better provide the polyfills via tslib (npm's promise-polyfill is tiny). Currently it's a bit confusing when the target in tsconfig says "es3" and the typescript language permits async, but then your code doesn't work in IE11. I think typescript providing a stable language with cross-browser support would be sooo huge. |
I am absolutely against that. Please polyfill yourself according to the browser targets you want to support, but don't put the additional library bloat on everyone by automatically polyfilling everything. |
Just opened another discussion, what should be filled or polyfilled by ts and what should not. |
It seems like this library depends on window.Promise being available. Is that true? Are there any other requirements for this library?
The text was updated successfully, but these errors were encountered: