-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Update core-js
#223
Update core-js
#223
Conversation
]), | ||
emplace: define("instance/emplace", [ | ||
"esnext.map.emplace", | ||
"esnext.weak-map.emplace", |
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.
With the current approach, it should be injected on constructors call, and that's already happening. Here are missed dependencies and in this way anyway it could cause a error. However, in case of pure mode + targets, injection on constructor call could fail because of #166.
]), | ||
endsWith: define("instance/ends-with", ["es.string.ends-with"]), | ||
entries: define("instance/entries", ArrayNatureIteratorsWithTag), | ||
every: define("instance/every", [ | ||
"es.array.every", | ||
"esnext.async-iterator.every", |
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.
Because lack of dependencies, it could cause a error, so this and similar cases commented. They are covered by AsyncIteratorProblemMethods
.
@nicolo-ribaudo could you publish a new release? |
No description provided.