fitBounds (and by extension, LngLatBounds.convert) should be compatible with GeoJSON bbox, turf.extent, etc. I.e., it should accept a single four-element array in [w, s, e, n] order.
Possibly fitBounds should also accept any GeoJSON and calculate the bounding box internally.
Most helpful comment
Possibly
fitBoundsshould also accept any GeoJSON and calculate the bounding box internally.