Package Exports
- react-google-maps
- 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/addons/MarkerWithLabel
- react-google-maps/lib/components/drawing/DrawingManager
- react-google-maps/lib/components/places/SearchBox
- react-google-maps/lib/components/places/StandaloneSearchBox
- react-google-maps/lib/components/visualization/HeatmapLayer
- react-google-maps/lib/constants
- 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
Introduction
Installation
Usage & Configuration
Changelog
The changelog is automatically generated via standard-version and can be found in project root as well as npm tarball.
Demo App
Getting Help
Before doing this, did you:
- Read the documentation
- Read the source code
You can get someone's help in three ways:
- Ask on StackOverflow with a google-maps tag or use react-google-maps as a keyword
- Ask in the chat room
- Create a Pull Request with your solutions to your problem
Please, be noted, no one, I mean, no one, is obligated to help you in ANY means. Your time is valuable, so does our contributors. Don't waste our time posting questions like “how do I do X with React-Google-Maps” and “my code doesn't work”. This is not the primary purpose of the issue tracker. Don't abuse.
For contributors
Some simple guidelines
- Don't manually modify
lib
folder. They're generated duringyarn release
process - Follow conventional-commits-specification
- standard-version
- Auto generated:
src/macros
->src/components
->lib/components
- Other components are manually maintained
- Use
yarn
and keepyarn.lock
updated in PR - Discuss! Discuss! Discuss!