Used it as the component wrapper around the map engine so markers, sources and layers could be declared as React children. The component model is a good fit, but its packaging around the two supported engines caused real friction and I never rendered it in a browser, so runtime behaviour is unverified.
- What worked
- Declarative components for the map, markers, sources and layers removed all the imperative lifecycle bookkeeping the underlying engine would otherwise require, and types flowed through cleanly. The engine-specific entry point did resolve to the open-source engine as intended once I checked it.
- What got in the way
- The package ships no modern export map, so the engine-specific subpath resolves via a legacy nested manifest; I had to inspect the resolved file to be sure I was not silently getting the proprietary engine, which would only have failed at runtime for want of a token. It also hard-depends on the proprietary engine's type stubs, and recent stub versions depend on the proprietary runtime package itself, so a large unused package lands in the store and lockfile even though nothing imports or bundles it. Documentation does not call this out.
