JSPM

  • Created
  • Published
  • Downloads 104929
  • Score
    100M100P100Q153078F
  • License MIT

React.js Google Maps integration component

Package Exports

  • react-google-maps
  • react-google-maps/lib/addons/InfoBox
  • react-google-maps/lib/addons/MarkerClusterer
  • react-google-maps/lib/async/withScriptjs
  • react-google-maps/lib/components/Circle
  • react-google-maps/lib/components/DirectionsRenderer
  • react-google-maps/lib/components/GoogleMap
  • react-google-maps/lib/components/Marker
  • react-google-maps/lib/components/OverlayView
  • react-google-maps/lib/components/addons/InfoBox
  • react-google-maps/lib/components/addons/MarkerClusterer
  • react-google-maps/lib/components/drawing/DrawingManager
  • react-google-maps/lib/components/places/SearchBox
  • react-google-maps/lib/components/visualization/HeatmapLayer
  • react-google-maps/lib/constants
  • react-google-maps/lib/places/SearchBox
  • react-google-maps/lib/utils/MapChildHelper
  • react-google-maps/lib/withGoogleMap
  • react-google-maps/lib/withScriptjs

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (react-google-maps) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

react-google-maps

React.js Google Maps integration component

Version Travis CI Quality Coverage Dependencies Gitter

Usage / Documentation

npm install --save react-google-maps

Then, read the documentation.

Changelog

The changelog is automatically generated via standard-version and can be found in project root as well as npm tarball.

Getting Help

For support or usage questions like “how do I do X with React-Google-Maps” and “my code doesn't work”, please search and ask on StackOverflow with a google-maps tag or use react-google-maps as a keyword first.

We ask you to do this because StackOverflow has a much better job at keeping popular questions visible. Unfortunately good answers get lost and outdated on GitHub.

Some questions take a long time to get an answer. If your question gets closed or you don't get a reply on StackOverflow for longer than a few days, we encourage you to post an issue linking to your question. We will close your issue but this will give people watching the repo an opportunity to see your question and reply to it on StackOverflow if they know the answer.

Please be considerate when doing this as this is not the primary purpose of the issue tracker.

For contributors

Some simple guidelines
  • Don't manually modify lib folder. They're generated during yarn release process
  • Follow conventional-commits-specification
  • standard-version
  • Auto generated: src/marcos -> src/components -> lib/components
  • Other components are manually maintained
  • Use yarn and keep yarn.lock updated in PR
  • Discuss! Discuss! Discuss!