Move or alias `#` directories for better ES Modules compatibility about es5-ext HOT 3 OPEN

@davidwallacejackson thanks for report. I can imagine how painful it can be.

The way it's being tackled is that new version of this package was published under ext name, and this one is free from this problem.

Still ofc packages that depend on es5-ext, also have to be updated. Unfortunately I do not have ETA on that. Which exactly packages (that depend on `es5-ext) impose an issue on your side?

Note it's technically a duplicate of #30

from es5-ext.

Thank you so much for responding so quickly! I'm sorry about missing those existing issues.

I didn't know about ext -- that sounds like the right path forward. There's four or five dependencies in my project using this package, but most of them are dev tooling, so I may not need to change those. The ones that are probably problematic are fantasticon and plotly.js. I'm going to dig in on those and see if their latest versions still use es5-ext -- if they do, I'll open PRs.

Oh, also: would it make sense to put some info about this issue and the new ext package in the project README?

Edit: after investigating fantasticon and plotly.js, it looks like the upstream dependencies that pull in this package are:

• https://github.com/medikoo/es6-weak-map
• https://github.com/medikoo/cli-color

If you have time to upgrade them, that'd be awesome! If not, I'll probably submit something myself in the next couple days 🙂

from es5-ext.

Thanks @davidwallacejackson

Problem is that also ext have not yet ported some stuff from es5-ext.

As I look in case of es6-weak-map it's only object/set-prototype-of that's missing (other missing things as object/is-value can be taken from type, they are not expected to be provided in ext)

In case of cli-color there's way more, and some imply different alternatives (as a lot of time passed and some native variants emerged in a meantime, e.g. instead of object/map or object/for-each we may refer to object/entries and work with that)

from es5-ext.