# About GmapVue

GmapVue is a fork from vue2-google-maps (opens new window).

This project has all features added to vue2-google-maps plugin up to v0.10.8 (opens new window), but in the case of gmap-vue it has the last features added to vue2-google-maps repository by the community developers in many PRs, that they can't landed in a new version of that project, for different reasons.

Because of that we fork the project and plain to continue working and adding new features to this great plugin.

# Installation

# npm

npm install gmap-vue --save

# yarn

yarn add gmap-vue

# Manually

Just download dist/gmap-vue.js file and include it from your HTML.

<script src="./gmap-vue.js"></script>

# jsdelivr

You can use a free CDN like jsdelivr (opens new window) to include this plugin in your html file

<script src="https://cdn.jsdelivr.net/npm/gmap-vue@1.2.2/dist/gmap-vue.min.js"></script>

# unpkg

You can use a free CDN like unpkg (opens new window) to include this plugin in your html file

<script src="https://unpkg.com/gmap-vue@1.2.2/dist/gmap-vue.js"></script>


Be aware that if you use this method, you cannot use TitleCase for your components and your attributes. That is, instead of writing <GmapMap>, you need to write <gmap-map>.

Source code - Live example (opens new window).

# Basic usage

# Get an API key from Google

Generating an Google Maps API key (opens new window).

# Exported utilities from the GmapVue plugin

In previous version the plugin exports all without any organization, from version 2 the plugin exports a default object with the install function required for Vue.js to install this plugin and two objects, helpers and components.

This two objects exports the same functions as before but in a better way, in the main.js file. The code below is a copy from that file.

 * Export all components and mixins
export const components = {

 * Export all helpers

export const helpers = {

# Quickstart (Webpack, Nuxt):

If you are using Webpack and Vue file components, just add the following to your code!

  :center="{lat:10, lng:10}"
  style="width: 500px; height: 300px"
    v-for="(m, index) in markers"

In your main.js or inside a Nuxt plugin:

import Vue from 'vue'
import GmapVue from 'gmap-vue'

Vue.use(GmapVue, {
  load: {
    key: 'YOUR_API_TOKEN',
    libraries: 'places', // This is required if you use the Autocomplete plugin
    // OR: libraries: 'places,drawing'
    // OR: libraries: 'places,drawing,visualization'
    // (as you require)

    //// If you want to set the version, you can do so:
    // v: '3.26',

  //// If you intend to programmatically custom event listener code
  //// (e.g. `this.$refs.gmap.$on('zoom_changed', someFunc)`)
  //// instead of going through Vue templates (e.g. `<GmapMap @zoom_changed="someFunc">`)
  //// you might need to turn this on.
  // autobindAllEvents: false,

  //// If you want to manually install components, e.g.
  //// import {GmapMarker} from 'gmap-vue/src/components/marker'
  //// Vue.component('GmapMarker', GmapMarker)
  //// then set installComponents to 'false'.
  //// If you want to automatically install all the components this property must be set to 'true':
  installComponents: true

# Getting a map reference

If you need to gain access to the Map instance (e.g. to call panToBounds, panTo):

  <GmapMap ref="mapRef" ...>
  export default {
    mounted () {
      // At this point, the child GmapMap has been mounted, but
      // its map has not been initialized.
      // Therefore we need to write mapRef.$mapPromise.then(() => ...)

      this.$refs.mapRef.$mapPromise.then((map) => {
        map.panTo({lat: 1.38, lng: 103.80})

# Accessing Google Maps API

If you need to access the Google maps API directly you can use the exported gmapApi() function like this

  <GmapMap ref="mapRef" ...>
    <GmapMarker ref="myMarker" :position="google && new google.maps.LatLng(1.38, 103.8)" />
import { gmapApi } from 'gmap-vue';

export default {
  name: 'your-component-name',
  computed: {
    // The below example is the same as writing
    // google() {
    //   return gmapApi();
    // },
    google: gmapApi,

You will get an object with a maps property and inside of it you can find all the Google maps API.

# Map Options

Control the options of the map with the options property. For more information about google MapOptions (opens new window) visit the link.

   zoomControl: true,
   mapTypeControl: false,
   scaleControl: false,
   streetViewControl: false,
   rotateControl: false,
   fullscreenControl: true,
   disableDefaultUi: false

# Region and language localization

To add region and language localization. For more information about google Localization (opens new window) visit the link.

Vue.use(GmapVue, {
  load: {
    region: 'VI',
    language: 'vi',

# Lazy loading

If you need to wait for google maps API to be ready, you can use the this.$gmapApiPromiseLazy() function to wait for it. This function is automatically added to your components when you use GmapVue plugin, also, you can find a reference of this function in your Vue instance if you have a reference of following common practice to assign it to vm variable.

A simple example

export default {
  name: 'your-component-name',
  data() {
    return {
      center: { lat: 4.5, lng: 99 },
      markers: [],
  async mounted() {
    // if you have a reference of Vue in a `vm` variable
    // the following option should work too
    // await vm.$gmapApiPromiseLazy();

    await this.$gmapApiPromiseLazy();
    this.markers = [
        location: new google.maps.LatLng({ lat: 3, lng: 101 }),
        weight: 100
        location: new google.maps.LatLng({ lat: 5, lng: 99 }),
        weight: 50
        location: new google.maps.LatLng({ lat: 6, lng: 97 }),
        weight: 80

# GmapMap slots

GmapMap component has two slots with a different behavior. The default slot is wrapped in a class that sets display: none; so by default any component you add to your map will be invisible.

This is ok for most of the supplied components that interact directly with the Google map object, but it's not good if you want to bring up things like toolboxes, etc.

There is a second slot named "visible" that must be used if you want to display content within the responsive wrapper for the map, hence that's why you'll see this in the drawing manager with slot example. It's actually not required in the first example because the default toolbox is part of the Google map object.

Thanks to @davydnorris (opens new window) to document this part of GmapVue.

# Nuxt.js config

For Nuxt.js projects, please import GmapVue in the following way:

import GmapVue from '~/node_modules/gmap-vue'

Add the following to your nuxt.config.js's build.extend():

transpile: [/^gmap-vue($|\/)/]


Please take a look at this example on stackblitz (opens new window)


# Officially supported components:

The list of officially support components are:

  • Rectangle, Circle
  • Polygon, Polyline
  • KML Layer
  • Marker
  • InfoWindow
  • Autocomplete
  • Cluster* (via marker-clusterer-plus)
  • Heat map
  • Drawing map: rectangle, circle, polygon, line

You can find examples of this on examples.

Auto-generated API documentation for these components are here (opens new window). (coming soon).

For Cluster, you must import the class specifically, e.g.

import GmapCluster from 'gmap-vue/dist/components/cluster' // replace dist with src if you have Babel issues

Vue.component('GmapCluster', GmapCluster)

Inconvenient, but this means all other users don't have to bundle the marker clusterer package in their source code.

# Adding your own components

It should be relatively easy to add your own components (e.g. Heatmap, GroundOverlay). please refer to the source code for mapElementFactory (opens new window).

Example for DirectionsRenderer (opens new window):

// DirectionsRenderer.js
import { helpers } from 'gmap-vue'
const { MapElementFactory } = helpers;

export default mapElementFactory({
  name: 'directionsRenderer',
  ctr: () => google.maps.DirectionsRenderer,
  //// The following is optional, but necessary if the constructor takes multiple arguments
  //// e.g. for GroundOverlay
  // ctrArgs: (options, otherProps) => [options],
  events: ['directions_changed'],

  // Mapped Props will automatically set up
  //   this.$watch('propertyName', (v) => instance.setPropertyName(v))
  // If you specify `twoWay`, then it also sets up:
  //   google.maps.event.addListener(instance, 'propertyName_changed', () => {
  //     this.$emit('propertyName_changed', instance.getPropertyName())
  //   })
  // If you specify `noBind`, then neither will be set up. You should manually
  // create your watchers in `afterCreate()`.
  mappedProps: {
    routeIndex: { type: Number },
    options: { type: Object },
    panel: { },
    directions: { type: Object },
    //// If you have a property that comes with a `_changed` event,
    //// you can specify `twoWay` to automatically bind the event, e.g. Map's `zoom`:
    // zoom: {type: Number, twoWay: true}
  // Any other properties you want to bind. Note: Must be in Object notation
  props: {},
  // Actions you want to perform before creating the object instance using the
  // provided constructor (for example, you can modify the `options` object).
  // If you return a promise, execution will suspend until the promise resolves
  beforeCreate (options) {},
  // Actions to perform after creating the object instance.
  afterCreate (directionsRendererInstance) {},

Thereafter, it's easy to use the newly-minted component!

  <GmapMap :zoom="..." :center="...">
    <DirectionsRenderer />
import DirectionsRenderer from './DirectionsRenderer.js'

export default {
  components: {DirectionsRenderer}

# Testing

More automated tests should be written to help new contributors.

Meanwhile, please test your changes against the suite of examples.

Improvements to the tests are welcome 😃