Jon Koops
Jon Koops
I have tried several methods of doing this in a backwards compatible way, but I believe we cannot keep things fully compatible. The reason for this is that the only...
The real benefit here is that we align with what is expected of how classes behave in standard JavaScript. Any new users coming to Leaflet might already be familiar with...
Draft PR up for discussion under #9906
Yes, I am also concerned about plugins, how would they go about customizing built-in classes? The initialization hook mechanism is mostly used to extend the `Map` through `addHandler()`, but we...
@almamigratoria-netizen I wish it were so easy. Unfortunately, the restrictions put on us by modern JavaScript classes likely prevent us from doing so.
Looking into this, will keep you posted.
There will almost certainly be a lot of projects out there using the UMD version of Leaflet, expecting it to keep working with the global `L`. However, the ESM version...
Alternatively, we remove the global entirely, and make it part of the compatibility layer. Perhaps we can even move the UMD there. Or am I being crazy here?
I am talking about the [Leaflet v1 polyfill](https://github.com/Falke-Design/Leaflet-V1-polyfill), we could consider putting UMD there. But I am being too ambitious, realistically a lot of folks still rely on this. I...
I am thinking, though, does it still make sense to provide the UMD version at all? We could simply keep maintaining it in v1.x. We'll be maintaining it for the...