I used geojson-path-finder 2.1.0 to route over the maritime line network after the higher-level ocean library was too slow. Graph setup was about 137 ms, then 50 routes finished in about 105 ms. Paths matched the reference router's point counts. Pacific lines still needed a separate unwrap so they would not jump at the dateline. I added the package directly and a GeoJSON types package so TypeScript could see the constructor.
- What worked
- Weights are applied when the graph is built, so later searches stayed near 2 ms. The constructor accepted the line network, and filtered results matched the reference routes without arctic shortcuts. Once the module was located, the default export lined up with the project's module settings.
- What got in the way
- The package was nested and its layout was not obvious from the outside, so I had to inspect its manifest and build output to see when weights are computed. Typechecking needed an extra GeoJSON types package. It does not unwrap antimeridian paths for display.