When map.fitBounds(...) is called with a bearing option passed in, it seems like the bearing is not taken into the account on calculating the appropriate zoom, resulting in part of the bounded area to not be in view.

mapbox-gl-js version: 1.12.0

browser: Chrome

Steps to Trigger Behavior

1. Create a bounded area with a list of coordinates
2. Call map.fitBounds(...) wi

'react-autocomplete' (https://github.com/reactjs/react-autocomplete) is no longer maintained and causing warnings

react-dom.development.js:12357 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.
• R

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

To access queryRenderedFeatures (which does not seem to be exposed on the MapGL comp) I currently make use of MapContext:

 <MapContext.Consumer>
          {map => {
            map.on("dragend", () => {
              const fe

There are some POIs without an icon, e.g.:

There are some new Maki icons, so it would be good to check if there are any new icons we could use for missing ones:

OpenMapTiles POI layer:
https://github.com/openmaptiles/openmaptiles/tree/master/layers/poi

Maki icons:
https://l

When you run npm test without setting the your access token in your local environment, you get the following error:

# directions
# initialized
ok 1 directions is initialized
# set/get inputs
not ok - Uncaught, unspecified "error" event. ([object Object])
http://localhost:58414/script.js:2069
        var err = new Error('Uncaught, unspecified "error" event. (' + er + ')');

To avoid annoyances like this I wonder if this plugin should add an event listener that is fired when elements have been added to the page

this.map.fire('accessibility.load');