Today we’re announcing the release of MapBox.js v1.1.0, which integrates with today’s release of Leaflet 0.6.1. This week has been the first official Leaflet code sprint, hosted at the MapBox office in DC with Leaflet’s creator, Vladimir Agafonkin.

When MapBox.js Switched to Leaflet in v1.0.0, we had bigger plans in mind - to invest in the core of Leaflet to make web mapping better for all. The ecosystem of Leaflet is one of the most important parts of building on an open plaform that has wide reach and a large community of developers and mappers. We’re making sure that Leaflet’s core is fast and flexible, so that open maps win.

Improving & Refining

Before MapBox.js v1.1.0, we relied on a post-0.5.1 version of Leaflet that wasn’t official tagged. Now that Leaflet 0.6.1 is tagged after 5 months of development, we can rely on a major version - and more importantly - distribute MapBox.js as a proper Leaflet plugin, without a bundled Leaflet.

MapBox.js v1.1.0 also includes many improvements to our thorough API Documentation, bugfixes, and improvements to the map API. This version also includes some changes that will make SSL support simpler and easier.

Leaflet gained many improvements in the push, including improvements from our original push on MapBox.js. Leaflet now uses mocha for testing, provides a wider array of layer getters and setters, and has improved behavior around map interaction. The project is also wisely staying small and simple by moving some previously-core functionality into plugins like Leaflet.draw

<iframe width=’100%’ height=300 src=’’> </iframe>

We also included a new control, L.mapbox.shareControl, which lets you add Facebook and Twitter share buttons to your map in one easy line.