I've reached some really interesting preliminary conclusions on the farmOS-map library-bundling/2.x front if folks are interested in following along;

* https://github.com/farmOS/farmOS-map/pull/112#issuecomment-850525841
* https://github.com/farmOS/farmOS-map/issues/68#issuecomment-851043516

TL;DR; My tentative conclusions are that farmOS-map 2.x should;

* **Do** make behaviors async and use lazy chunks for the included behaviors - allows farmOS-map core behaviors to keep growing without necessarily incurring incremental performance costs for all use-cases
* **Do** remove core support for Google maps - a related change should involve packaging up Google maps as an optional contrib module
* **Not** externalize to `ol.js` - this is expensive from a performance perspective and would involve depending on a legacy packaging option for OpenLayers
* **Not** adopt Webpack Module Federation for OpenLayers at this time - this seems elegant, but in practice the tooling isn't there yet to intelligently tune the chunks sizes for a large dependency like OpenLayers