Vector-Tiles-Google-Maps
Vector-Tiles-Google-Maps copied to clipboard
Add dependency framework, build process, tests, and other reworks
Hello,
We at NorthPoint Development recent forked this project for use in an internal project, as we needed a good library for rendering vector tiles to our Google Maps application. During the implementation we made a number of changes we'd like to share in this PR.
At a high level:
- Changes the project architecture to use ES6 modules, add
npmfor dependency management, and import thepbfand@mapbox/vector-tiledependencies. - Adds
jestfor unit testing and adds a number of unit tests to avoid regressions inMVTFeature,MVTLayer, andMVTSource. - Adds ESLint for code linting, along with standard config.
- Adds a new build process leveraging
vite: relevant code and packages are minified and written tovector-tiles-google-maps/distwhennpm run buildis executed. - Adds JSDoc types and extended documentation.
- Adds logic to load the Google Maps API key from local storage instead of hardcoding to each example page, and shortcuts to all examples from
index.html. - Removes some Visual Studio boilerplate files that were not being used.
We would be happy to answer any questions you have about these changes!