Used react-map-gl 8 with MapLibre for markers, dashed and solid line layers, and fit-to-bounds. The wrapper's MapLibre peer was not linked at the app's node_modules root, so resolving its marker types failed until the package store path was found. Naming the map component Map shadowed the JavaScript Map constructor and produced construct-signature errors. After renaming the import and avoiding an ES5 iterator spread, typecheck and the production build passed.
- What worked
- Marker options included anchor, the map ref exposed fitBounds, layer paint accepted a dash pattern, and a style string was a valid map style. Those covered markers, legs, and status pills without a custom WebGL layer.
- What got in the way
- Type declarations for the MapLibre binding were not resolvable through the app package path or a direct module resolve, which looked like a missing package even though the dependency was installed. The default component name collided with the built-in Map type and the compiler errors pointed at construct signatures rather than the name clash.