Featuregrid imports `toLatLngBounds` which leaflet exports as `latLngBounds`.

Describe the bug

In the latest version of esri-leaflet, FeatureGrid.js imports toLatLngBounds from leaflet, which is not exported by leaflet 1.6.0. It is exported as latLngBounds. This results in an error in our rollup build. See the following logs:

[!] Error: 'toLatLngBounds' is not exported by node_modules/leaflet/dist/leaflet-src.esm.js
https://rollupjs.org/guide/en/#error-name-is-not-exported-by-module
node_modules/esri-leaflet/src/Layers/FeatureLayer/FeatureGrid.js (3:2)
1: import {
2:   LatLngBounds,
3:   toLatLngBounds as latLngBounds,
     ^
4:   Layer,
5:   Browser,
Error: 'toLatLngBounds' is not exported by node_modules/leaflet/dist/leaflet-src.esm.js

We temporarly fixed it with an automatic replacement of the codeline after the installation of the npm modules.

Expected behavior

I expect the FeatureGrid.js to import latLngBounds instead of toLatLngBounds. You can see the export of toLatLngBounds as latLngBounds in the leaflet repository.

Environment Information

• Version of Leaflet (1.6.0):
• Version of Esri Leaflet (2.4.0):
• Your OS: [macOS]
• Browser and Version (error occurs on build time)

Additional context

We are working on an angular component library which is bundled by rollup and built by bazel.

[gavinr]

@nisarmd If you’ve just started seeing it, I think your issue is probably the same as in this thread: https://github.com/Esri/esri-leaflet/issues/1342#issuecomment-1255277662

[nisarmd]

@jwasilgeo Started seeing this issue with the following versions -

• node.js v16.16.0
• @types/esri-leaflet v2.1.9
• @types/leaflet v1.8.0
• esri-leaflet v3.0.8

Log - node_modules/esri-leaflet/src/Layer/FeatureLayer/FeatureGrid.js - Error: export ‘toLatLngBounds’ (imported as ‘latLngBounds’) was found in ‘leaflet’