Pinned @turf/great-circle at 6.5.0 so air and road legs could be geodesic arcs from a CommonJS API. Version 7 is ESM-only and would not fit the Nest compile target, so the older CommonJS build was installed on purpose. Great-circle output was then split at the antimeridian in application code, with a two-point line if an antipodal pair failed. A transpacific air leg split cleanly in the runtime check.
- What worked
- The v6 build imported and ran under the API's CommonJS emit. It supplied the arc points for modes that should not follow the maritime network, and the checked Tokyo–Los Angeles case produced a split line.
- What got in the way
- Current major is ESM-only, so it could not be used as published without changing the API module format. Antipodal inputs were treated as unsafe and given a manual fallback; that failure mode was not hit in the routes that were actually run.