Jovica Markoski

I agree it's somewhat hard to read, but I'm not sure what you are referring to how I should modify it, may you please be more specific? Thanks.

@existentialism What do you think about the new version?

Yes, that's way better and more readable, I agree. Will change it to that format.

I will try to clarify in details about what happens exactly and why. First, `core-js` exposes two packages that are relevant in this context and they are: `core-js` and `core-js-pure`....

Oh, I messed up the links. They are fixed now. PS: You are welcome, I'm glad if it helped.

I'm sorry for responding late guys. @elyobo Thanks, I'm glad if my answer helped. I'm not aware of such explanation in the docs/issues, my understanding comes from reading the source...

Another solution is to switch from `useBuiltIns: 'usage'` to `useBuiltIns: 'entry'`, since you are okay with global `core-js` pollution. You can add only `import 'core-js'` in the entry point, and...

No, it won't. Adding import to `core-js` will pollute the global environment, and the single line import will convert to more granular imports from the `core-js` library based on your...

@dangreen I'm not sure I understood correctly what is the problem you are trying to solve, but I'll try to explain the philosophy of using the `@babel/preset-env` with `useBuiltIns: 'usage'`...

@dangreen Copy-paste from my answer given in (linked in the above comment) : [https://github.com/babel/babel/issues/9853#issuecomment-619587386](https://github.com/babel/babel/issues/9853#issuecomment-619587386) > **Library**: If you are authoring a library, use only `@babel/transform-runtime` with `corejs` option plus `@babel/runtime-corejs3`...