Target Use Case
Restructure the package to better handle the increasing divergence of the Maplibre and Mapbox APIs.
The current 7.x type-sharing system is not compatible with mapbox-gl v3.5 official types and some maplibre-gl v5.0 breaking changes.
Proposal
The code base will be split into independent implementations for mapbox-gl and maplibre-gl wrappers. There will be 3 endpoints exported:
react-map-gl/maplibre: Maplibre wrapper, compatible with maplibre-gl@>=4. It is also independently published as @vis.gl/react-maplibre. An alpha release is available for testing here.
react-map-gl/mapbox: Mapbox wrapper, compatible with mapbox-gl@>=3.5.0. It will also be independently published as @vis.gl/react-mapbox.
react-map-gl/mapbox-legacy: the legacy Mapbox wrapper, compatible with mapbox-gl v1.x and v2.x.
Support for maplibre-gl v3 and older will be deprecated because we're not aware of appealing reasons/significant blockers against upgrading. Please reply to this thread if you have a special use case.
Target Use Case
Restructure the package to better handle the increasing divergence of the Maplibre and Mapbox APIs.
The current 7.x type-sharing system is not compatible with mapbox-gl v3.5 official types and some maplibre-gl v5.0 breaking changes.
Proposal
The code base will be split into independent implementations for mapbox-gl and maplibre-gl wrappers. There will be 3 endpoints exported:
react-map-gl/maplibre: Maplibre wrapper, compatible withmaplibre-gl@>=4. It is also independently published as@vis.gl/react-maplibre. An alpha release is available for testing here.react-map-gl/mapbox: Mapbox wrapper, compatible withmapbox-gl@>=3.5.0. It will also be independently published as@vis.gl/react-mapbox.react-map-gl/mapbox-legacy: the legacy Mapbox wrapper, compatible withmapbox-glv1.x and v2.x.Support for
maplibre-glv3 and older will be deprecated because we're not aware of appealing reasons/significant blockers against upgrading. Please reply to this thread if you have a special use case.