Per Liedman
Per Liedman
The issue is with how webpack handles bundling of mixed CommonJS and ESM dependencies, not with geojson-path-finder. Please try the new version 2.0.0 of geojson-path-finder and see if it helps.
Maybe old news, and not related to GraphHopper, but this talk shows some of the difficulties (and maybe possible solutions) in routing over areas: https://www.youtube.com/watch?v=chGlRnYGvDg
@mourner while they look similar, do you think it's really the same issue? #2021 occured because the transition end event was never fired unless `requestAnimFrame` was called, causing the map...
Some notes after inspecting this problem: - The same problem is reproducible with Leaflet 0.6.0, so it's been there for a long time - When animation is enabled, the map's...
@Jmuccigr that is the expected behaviour. `fitBounds` will only animate if the point is close on the same zoom level (https://github.com/Leaflet/Leaflet/blob/master/src/map/Map.js#L1520) or the zoom level is within a threshold (https://github.com/Leaflet/Leaflet/blob/master/src/map/Map.js#L1575);...
The original issue is still reproducible in @theashyster's playground example. I think [my explanation here](https://github.com/Leaflet/Leaflet/issues/3249#issuecomment-75931374) is still a valid description of why this happens, but we need to figure out...
@atlantageek I guess we theoretically could but 1. we don't use a lot of callbacks for async stuff in other places, so it is sort of against the Leaflet style...
@maxdeepfield no plans, as far as I know. I'd be happy to guide if someone would be willing to take this on.
It sounds like an oversight in the current design that it does not take direction into account, probably because my requirement for edge datas came up in a separate project...
No worries, I'm more than familiar with the feeling :sweat_smile: