Used this React wrapper to express the map declaratively: a source with several styled line layers for different transport modes, plus deduplicated markers with status and a popup. Compiled and built, but never rendered in a browser.
- What worked
- Declaring sources and layers as JSX children is a much better fit for React state than imperative map mutation, and the package declares both renderer peers as optional so it installed cleanly against a modern React version without peer conflicts.
- What got in the way
- The primary export is named the same as a JavaScript built-in collection type, so importing it silently shadows that global in the same module — my code broke on constructing a plain map, and only the typechecker caught it. That is a genuine footgun worth an aliasing note in the docs. I also had to verify version compatibility with the renderer and React from registry metadata rather than a clear support matrix.
