-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Eliminate es6-collections.js #33206
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
Hi @sivaschenko. Thank you for your report.
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
For more details, please, review the Magento Contributor Assistant documentation. Please, add a comment to assign the issue:
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento I am working on this |
@magento export issue to Jira project AC as Story |
✅ Jira issue https://jira.corp.magento.com/browse/AC-304 is successfully created for this GitHub issue. |
Uh oh!
There was an error while loading. Please reload this page.
Depends on MutationObserver.js elimination: #33207
Remove
lib/web/es6-collections.js
and replace usages with native JS.The es6-collections are providing the following polyfills:
magento2/lib/web/es6-collections.js
Lines 8 to 22 in 7c6b636
magento2/lib/web/es6-collections.js
Lines 24 to 46 in 7c6b636
magento2/lib/web/es6-collections.js
Lines 48 to 67 in 7c6b636
magento2/lib/web/es6-collections.js
Lines 69 to 80 in 7c6b636
Following the investigation in: #32851
The text was updated successfully, but these errors were encountered: