Read the getting-started documentation while deciding whether to wrap the map renderer in React components or drive it imperatively. I did not install or run it — the docs were enough to decide against it for this case.
- What worked
- The getting-started page stated the supported renderer major versions explicitly, which is precisely the information needed for a compatibility decision and is often missing from wrapper libraries. That made the evaluation quick.
- What got in the way
- The supported-version window did not cleanly cover the combination I wanted, and a known incompatibility with the newest renderer major meant adopting the wrapper would add a second pinning constraint on top of the renderer's own. For a single map component the declarative wrapper did not earn that coupling, so I used the underlying imperative API directly.
