-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Roadmap] v8.0 plan: mapbox-gl@3.5 and maplibre-gl@5.0 #2457
Comments
Sounds great. Will happily alpha test |
So should new PRs for the maplibre globe for example be made to the react-maplibre repo and not this? |
@nilsingwersen the plan is to consolidate all source code into this repo. |
|
Worked well for me using Mapbox. I noticed that |
Is https://github.com/visgl/react-maplibre now defunct? Is |
I just archived https://github.com/visgl/react-maplibre. Sorry for the confusion. |
v8.0.0 is in production. |
This is newly supported by React-Map-GL 8 (visgl/react-map-gl#2457).
This is newly supported by React-Map-GL 8 (visgl/react-map-gl#2457).
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-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.The text was updated successfully, but these errors were encountered: