The weird part is that you were always violating your contract with Mapbox by circumventing their billing code[0], so now you just have a copyright violation added on top of that. The way to bypass it is identical to what it was before.

But, the big change is in their issue[1] they opened about it:

> Can I still use self-hosted map tiles?

> Yes. Developers simply need a Mapbox account and access token to use this v2.

>

> Can I use data or tiles from Google Maps or other non-Mapbox services?

> Yes. GL JS is fully interoperable with third party map sources that provide vector or raster tiles in supported formats. Usage of v2 is billed by Map Load to the Mapbox account owner. The license terms make no distinction between data sources.

They're charging for Mapbox GL JS, even if you don't actually use their tiles.

[0]: https://github.com/mapbox/mapbox-gl-js/blob/c7ed000f6d628531...

[1]: https://github.com/mapbox/mapbox-gl-js/issues/10162

I guess they don't like that people can generate their own vector tiles more easily nowadays, or services like Maptiler [0] (see [1] for some more context) that provide tiles at lower costs.

[0]: https://www.maptiler.com/mapbox-alternative/

[1]: https://www.maptiler.com/news/2020/05/the-future-of-openmapt...