Mercator. Getting boundary values by longitude about d3-geo

[mbostock]

You can’t rely on [190,0] being distinct from [-170, 0]; they represent the same point on the sphere. Same with [-180, 0] and [180, 0]; it’s somewhat coincidental that it works in this case due to floating point. If you want to compute the bounds of something, use path.bounds, say with {type: "Sphere"} for the entire globe.

[dowhileforeach]

Mike, thank you for the hint about using path.bounds.
As a result, the boundary values of the mercator, expressed in geographical coordinates, now I get this way:

function mercatorGeoBounds(lambda: number) {
  const geoToProj = geoMercator().rotate([lambda, 0, 0]);
  const projToGeo = geoToProj.invert;
  const [leftTopBoundPointOnProj, rightBottomBoundPointOnProj] = geoPath().projection(geoToProj).bounds({type: 'Sphere'});
  const leftTopBoundPoint = projToGeo(leftTopBoundPointOnProj);
  const rightBottomBoundPoint = projToGeo(rightBottomBoundPointOnProj);

  const [lonLeft, latTop] = leftTopBoundPoint;
  return {
    lonLeft,
    lonRight: (lonLeft + 360) - 0.000000000001,
    latTop,
    latBottom: rightBottomBoundPoint[1],
  };
}