Denis Pushkarev

@fabiospampinato it will not work this way. Fundamental features implemented internally and entry points like `es6.object.define-property` is just a facade.

@thiagodp it's absolutely not related to this issue and can't help here - for example, `es-shims` project use what you propose, but susceptible to this problem even more than `core-js`.

@thiagodp > Separating into individual modules is a way to refactoring them and to pruning unneeded dependencies. Sorry, but not in this case. Rather here will be a backward effect...

@thiagodp if you are wondering what this problem looks with the separate packages approach, see https://github.com/es-shims/AggregateError/issues/13

@matzeeable it's not related to this issue. `Object.keys` is polyfilled in IE11 since it's implemented not properly by the latest spec of the language.

I'm thinking about adding it to `core-js@4`.

After adding all `core-js` entries to this field, CI randomly dies (2 / 3 chance) on MacOS https://github.com/zloirock/core-js/actions/runs/432880677 - seems 3k+ entries in this field is too much -/ (sure,...

Removing some unnecessary entries allowed to reduce the number of patterns to a reasonable number.

I'll think about it. However, I'm not sure.

@longlho done.