by miguelcobain

miguelcobain / ember-leaflet

:fire: :leaves: Easy and declarative mapping for ember

202 Stars 79 Forks Last release: Not found MIT License 458 Commits 54 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

ember-leaflet Build Status Ember Observer Score npm version

Ember-Leaflet aims to make working with Leaflet layers in your Ember app as easy, declarative and composable as templates make working with DOM.


Ember Leaflet works in Ember 1.13.9+ with no deprecations.

To install it run:

ember install ember-leaflet

This will also add the

package to your project. If you're upgrading from a previous version of
, you can safely remove the
dependency from your
and add it to

If you require a legacy support version of leaflet or need a specific version for other reasons, you can just install that version via npm / yarn:

npm install --save-dev [email protected]
yarn add -D [email protected]

Support, Questions, Collaboration

Discord Join Ember on Discord


Documentation and examples are hosted at https://miguelcobain.github.io/ember-leaflet/. Please file any issues if you see that something can be improved.

If you're looking for the previous ember-leaflet version, you can use this repo.

Production Builds

In your ember-cli-build.js add the following snippet:

  var app = new EmberApp(defaults, {
    // Add options here
    fingerprint: {
      exclude: [
Ember-Cli does fingerprinting (appending an md5 checksum to the end of every file) for production builds by default (http://ember-cli.com/user-guide/#fingerprinting-and-cdn-urls). Exclude the assets you need so that your production build produces them correctly.


Web apps frequently need to display geographic data, especially if it has a direct relationship with the real world. That isn't new, and has been done previously in all kinds of formats, particularly with raster and vector data.

Ember apps naturally may have the same requirements and until now, devs have been either using mapping libraries outside of ember scope, or using previous versions of ember-leaflet.

The problem was that both approaches were hard. Frequently existing libraries have regular javascript imperative APIs and html in mind. We all know and love how ember makes us flow the data in our app. Previous approaches simply didn't fit where ember really shines: templates, actions, routing, and above all, expressiveness.

Ember-leaflet allows you to express your maps right in your templates. Also, it is streamlined for ember in general. You have things like actions, components and the ability to use regular handlebars helpers like


We can't go wrong with delegating the mapping part to the battle tested, performant and lightweight Leaflet library.

So, let the mapping begin.


Think of your map as a set of layers inside a container. Your main container will be the

 component. This component creates the map container where your tiles, vectors and markers will be added to. Let's see an example of how it looks:


<layers.marker as> <marker.popup>

The Oregon Convention Center

777 NE Martin Luther King Jr Blvd
Portland, OR 97232 </marker.popup> </layers.marker>

<layers.marker as> <marker.popup>


</marker.popup> </layers.marker>



  • npm run lint:js
  • npm run lint:js -- --fix

Running tests

  • ember test
    – Runs the test suite on the current Ember version
  • ember test --server
    – Runs the test suite in "watch mode"
  • ember try:each
    – Runs the test suite against multiple Ember versions

Running the dummy application

For more information on using ember-cli, visit https://ember-cli.com/.


See the Contributing guide for details.


This project is licensed under the MIT License.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.