Luke Deen Taylor
Luke Deen Taylor
`maplibre-gl-leaflet` is a wrapper around `maplibre-gl-js`, so to my understanding any features it implements are supported by `maplibre-gl-js`. do you have any examples of the missing features we need?
I’m optimistic that all of these things can be built efficiently with maplibre-gl-js, and many of them can even provide _better_ interoperability with the map in a “vector-native” environment compared...
As an aside, although I haven’t contributed to this codebase in the past, I have some experience building interactive vector map applications with these tools, and I’d be enthusiastic about...
tbf most of that diff was the addition of leaflet itself to `vendor`, but agree it’s a big effort.
My original idea _was_ to “use two separate map display libraries on the same page” — we could switch out / instantiate the underlying map implementation when the user switches...
I think you’re right; I’ve updated the original issue, and added additional details
Well, in principle it’s possible to feature-detect webgl support, and then skip initializing the client-rendered maps when the layers pane is opened where webgl is unsupported.
Actually, it seems like declaration support for JS files / JSDoc is working; a fresh build of tsgo transforms this `.js` file ```js /** * @param {number} a * @param...
got it, awesome! I did notice that tsgo emits `export declare function` statements for that .js file, where tsc emitted plain `export function` statements (but both use `export declare` in...