-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Data for stage 3 iterator-helpers #20573
Conversation
It's enabled by default in beta 117 and |
Thanks @zloirock. I updated the version. Hope this is how BCD works |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good @Josh-Cena; just a few comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Josh-Cena just one more small nitpick.
Neither of us have permissions to BCD so we'll have to wait for maintainers :( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now, thanks @Josh-Cena!
Thanks, all, merging shortly 👍🏻 |
V8 unshipped it https://bugs.chromium.org/p/chromium/issues/detail?id=1474613. |
I'm aware of the unfortunate situation: tc39/proposal-iterator-helpers#286 I'm not sure how it should be documented. Maybe just change |
I'd stay tuned until next week, though I understand that's cutting it close. If Transcend can ship a fix on their CDN and we can confirm the fix, then Chrome will continue to ship in 117. Otherwise we will delay. |
Thanks! Please keep us posted so we may update the data accordingly. |
Summary
mdn/content#28677
@chrisdavidmills The Chrome version needs to be updated. Is it 118? 117?
Test results and supporting details
Related issues