0.7.8

.eslintrc

@@ -0,0 +1,21 @@
+{
+  "globals": {
+    "L": true,
+  },
+  "env": {
+    "commonjs": true,
+    "amd": true,
+    "node": false
+  },
+  "extends": "mourner",
+  "rules": {
+    "no-mixed-spaces-and-tabs": [2, "smart-tabs"],
+    "indent": [2, "tab", {"VariableDeclarator": 0}],
+    "curly": 2,
+    "spaced-comment": 2,
+    "strict": 0,
+    "wrap-iife": 0,
+    "key-spacing": 0,
+    "consistent-return": 0
+  }
+}

.github/workflows/npmpublish.yml

@@ -0,0 +1,45 @@
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+      - run: npm ci
+      - run: npm test
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.npm_token}}
+
+  publish-gpr:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v1
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://npm.pkg.github.com/
+          scope: '@your-github-username'
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

.gitignore

@@ -7,9 +7,12 @@ tmp/**/*
 *.sublime-*
 _site
 dist/*.js
+dist/*.map
+dist/reference.html
 coverage/
 *.js.html
 index.html
 .mailmap
 bower.json
-component.json
+component.json
+debug/local/

.npmignore

@@ -7,3 +7,4 @@ tmp/**/*
 *.sublime-*
 _site
 coverage/
+dist/leaflet.zip

.travis.yml

@@ -1,6 +1,6 @@
 sudo: false
 language: node_js
-node_js: 0.12
+node_js: stable
 addons:
   artifacts:
     paths:

CNAME

@@ -0,0 +1 @@
+leafletjs.com

CONTRIBUTING.md

@@ -4,18 +4,21 @@ Contributing to Leaflet
  1. [Getting Involved](#getting-involved)
  2. [Reporting Bugs](#reporting-bugs)
  3. [Contributing Code](#contributing-code)
- 4. [Improving Documentation](#improving-documentation)
+ 4. [Running the Tests](#running-the-tests)
+ 6. [Improving Documentation](#improving-documentation)
+ 7. [Code of Conduct](#code-of-conduct)
+ 8. [Thank You](#thank-you)
 
 ## Getting Involved
 
-Third-party patches are absolutely essential on our quest to create the best mapping library that will ever exist.
-However, they're not the only way to get involved with the development of Leaflet.
-You can help the project tremendously by discovering and [reporting bugs](#reporting-bugs),
-[improving documentation](#improving-documentation),
-helping others on the [Leaflet forum](https://groups.google.com/forum/#!forum/leaflet-js)
-and [GitHub issues](https://github.com/Leaflet/Leaflet/issues),
-showing your support for your favorite feature suggestions on [Leaflet UserVoice page](http://leaflet.uservoice.com),
-tweeting to [@LeafletJS](http://twitter.com/LeafletJS)
+Third-party patches are absolutely essential in our quest to create the best mapping library that will ever exist.
+However, they're not the only way to get involved with Leaflet development.
+You can help the project tremendously by discovering and [reporting bugs](#reporting-bugs);
+[improving documentation](#improving-documentation);
+helping others on [Stack Overflow](https://stackoverflow.com/questions/tagged/leaflet),
+[GIS Stack Exchange](https://gis.stackexchange.com/questions/tagged/leaflet)
+and [GitHub issues](https://github.com/Leaflet/Leaflet/issues);
+tweeting to [@LeafletJS](http://twitter.com/LeafletJS);
 and spreading the word about Leaflet among your colleagues and friends.
 
 ## Reporting Bugs
@@ -26,34 +29,34 @@ first make sure that your issue is caused by Leaflet, not your application code
 Second, search the already reported issues for similar cases,
 and if it's already reported, just add any additional details in the comments.
 
-After you made sure that you've found a new Leaflet bug,
+After you've made sure that you've found a new Leaflet bug,
 here are some tips for creating a helpful report that will make fixing it much easier and quicker:
 
  * Write a **descriptive, specific title**. Bad: *Problem with polylines*. Good: *Doing X in IE9 causes Z*.
  * Include **browser, OS and Leaflet version** info in the description.
- * Create a **simple test case** that demonstrates the bug (e.g. using [JSFiddle](http://jsfiddle.net/)).
+ * Create a **simple test case** that demonstrates the bug (e.g. using [Leaflet plunker](http://leafletjs.com/edit.html)).
  * Check whether the bug can be reproduced in **other browsers**.
  * Check if the bug occurs in the stable version, master, or both.
  * *Bonus tip:* if the bug only appears in the master version but the stable version is fine,
    use `git bisect` to find the exact commit that introduced the bug.
 
 If you just want some help with your project,
-try asking [on the Leaflet forum](https://groups.google.com/forum/#!forum/leaflet-js) instead.
+try asking on [Stack Overflow](https://stackoverflow.com/questions/tagged/leaflet)
+or [GIS Stack Exchange](https://gis.stackexchange.com/questions/tagged/leaflet) instead.
 
 ## Contributing Code
 
 ### Considerations for Accepting Patches
 
-While we happily accept patches, we're also commited to keeping Leaflet simple, lightweight and blazingly fast.
+While we happily accept patches, we're also committed to keeping Leaflet simple, lightweight and blazingly fast.
 So bugfixes, performance optimizations and small improvements that don't add a lot of code
 are much more likely to get accepted quickly.
 
-Before sending a pull request with a new feature, first check if it's been discussed before already
-(either on [GitHub issues](https://github.com/Leaflet/Leaflet/issues)
-or [Leaflet UserVoice](http://leaflet.uservoice.com/)),
-and then ask yourself two questions:
+Before sending a pull request with a new feature, check if it's been discussed before already
+on [GitHub issues](https://github.com/Leaflet/Leaflet/issues)
+and ask yourself two questions:
 
- 1. Are you sure that this new feature is important enough to justify its presense in the Leaflet core?
+ 1. Are you sure that this new feature is important enough to justify its presence in the Leaflet core?
     Or will it look better as a plugin in a separate repository?
  2. Is it written in a simple, concise way that doesn't add bulk to the codebase?
 
@@ -62,16 +65,17 @@ please consider submitting another pull request with the corresponding [document
 
 ### Setting up the Build System
 
-To set up the Leaflet build system, install [Node](http://nodejs.org/),
-then run the following commands in the project root:
+The Leaflet build system uses [NodeJS](http://nodejs.org/).
+To set up the Leaflet build system, install [NodeJS](https://nodejs.org/).
+Then run the following commands in the project root to install dependencies:
 
 ```
-npm install -g jake
 npm install
 ```
-
-You can build minified Leaflet by running `jake` (it will be built from source in the `dist` folder).
-For a custom build with selected components, open `build/build.html` in the browser and follow the instructions from there.
+or, if you prefer [`yarn`](https://yarnpkg.com/) over `npm`:
+```
+yarn install
+```
 
 ### Making Changes to Leaflet Source
 
@@ -85,71 +89,113 @@ Please do not commit to the `master` branch, or your unrelated changes will go i
 You should also follow the code style and whitespace conventions of the original codebase.
 In particular, use tabs for indentation and spaces for alignment.
 
-Before commiting your changes, run `jake lint` to catch any JS errors in the code and fix them.
+Before committing your changes, run `npm run lint` to catch any JS errors in the code and fix them.
 If you add any new files to the Leaflet source, make sure to also add them to `build/deps.js`
 so that the build system knows about them.
 
 Also, please make sure that you have [line endings configured properly](https://help.github.com/articles/dealing-with-line-endings) in Git! Otherwise the diff will show that all lines of a file were changed even if you touched only one.
 
 Happy coding!
 
-## Running the Tests
+### Using RollupJS
 
-To run the tests from the command line,
-install [PhantomJS](http://phantomjs.org/) (and make sure it's in your `PATH`),
-then run:
+The source JavaScript code for Leaflet is a few dozen files, in the `src/` directory.
+But normally, Leaflet is loaded in a web browser as just one JavaScript file.
 
-```
-jake test
-```
+In order to create this file, run `npm run rollup` or `yarn run rollup`.
 
-To run all the tests in actual browsers at the same time, you can do:
+You'll find `dist/leaflet-src.js` and `dist/leaflet.js`. The difference is that
+`dist/leaflet-src.js` has sourcemaps and it's not uglified, so it's better for
+development. `dist/leaflet.js` is uglified and thus is smaller, so it's better
+for deployment.
+
+When developing (or bugfixing) core Leaflet functionalities, it's common to use
+the webpages in the `debug/` directory, and run the unit tests (`spec/index.html`)
+in a graphical browser. This requires regenerating the bundled files quickly.
+
+In order to do so, run `npm run watch` or `yarn run watch`. This will keep
+on rebuilding the bundles whenever any source file changes.
+
+## Running the Tests
+
+To run the tests from the command line, first make sure you have installed all
+the build system requirements with `npm install`. Then, simply run:
 
 ```
-jake test --ff --chrome --safari --ie
+npm test
 ```
 
-To run the tests in a browser manually, open `spec/index.html`.
-
-## Code Coverage
+By default, the tests will run in [PhantomJS](http://phantomjs.org/), and also
+in [SlimerJS](https://slimerjs.org/) if possible. If `npm test` complains about
+PhantomJS, install it manually and make sure it's in your `PATH`.
 
-To generate a detailed report about test coverage (which helps tremendously when working on test improvements), run:
+To run all the tests in actual browsers at the same time, you can do:
 
 ```
-jake test --cov
+npm test -- -- --browsers Firefox,Chrome,Safari,IE
 ```
 
-After that, open `spec/coverage/<environment>/index.html` in a browser to see the report.
-From there you can click through folders/files to get details on their individual coverage.
+(Note: the doubling of "`--`" [special option](https://docs.npmjs.com/cli/run-script#description) is [important](https://github.com/Leaflet/Leaflet/pull/6166#issuecomment-390959903))
+
+To run the tests in a browser manually, open `spec/index.html`.
 
 ## Improving Documentation
 
-The code of the live Leaflet website that contains all documentation and examples is located in the `gh-pages` branch
-and is automatically generated from a set of HTML and Markdown files by [Jekyll](https://github.com/mojombo/jekyll).
+The code of the live Leaflet website that contains all documentation and examples is located in the `docs/` directory of the `master` branch
+and is automatically generated from a set of HTML and Markdown files by [Jekyll](http://jekyllrb.com/).
 
 The easiest way to make little improvements such as fixing typos without even leaving the browser
 is by editing one of the files with the online GitHub editor:
-browse the [gh-pages branch](https://github.com/Leaflet/Leaflet/tree/gh-pages),
-choose a certain file for editing (e.g. `reference.html` for API reference),
+browse the [`docs/ directory`](https://github.com/Leaflet/Leaflet/tree/master/docs),
+choose a certain file for editing (e.g. `plugins.md` for the list of Leaflet plugins),
 click the Edit button, make changes and follow instructions from there.
 Once it gets merged, the changes will immediately appear on the website.
 
 If you need to make edits in a local repository to see how it looks in the process, do the following:
 
- 1. [Install Ruby](http://www.ruby-lang.org/en/) if don't have it yet.
+ 1. [Install Ruby](http://www.ruby-lang.org/en/) if you don't have it yet.
  2. Run `gem install jekyll`.
- 3. Run `jekyll serve --watch` in the root `Leaflet` folder.
- 4. Open `localhost:4000` in your browser.
+ 3. Enter the directory where you cloned the Leaflet repository
+ 4. Run `bundle install`
+ 5. Make sure you are in the `master` branch by running `git checkout master`
+ 6. Enter the documentation subdirectory by running `cd docs`
+ 7. Run `jekyll serve --watch`.
+ 8. Open `localhost:4000` in your web browser.
 
 Now any file changes will be updated when you reload pages automatically.
-After commiting the changes, just send a pull request.
+After committing the changes, just send a pull request.
+
+### API documentation
+
+Since Leaflet 1.0.0-rc1, the API documentation in `reference-1.0.0.html` is handled
+via [Leafdoc](https://github.com/Leaflet/Leafdoc). This means that next to the
+code for every method, option or property there is a special code comment documenting
+that feature. In order to edit the API documentation, just edit these comments in the
+source code.
+
+In order to generate the documentation, make sure that the development dependencies
+are installed (run either `npm install` or `yarn install`), then just run
+
+```
+npm run docs
+```
+
+and you'll find a `.html` file in the `dist/` directory.
+
+On every release of a new Leaflet version, this file will be generated and copied
+over to `docs/reference.html` - there is no need to send pull requests with changes to this file to update the API documentation.
+
+## Code of Conduct
 
-If you need to update documentation according to a new feature that only appeared in the master version (not stable one),
-you need to make changes to `gh-pages-master` branch instead of `gh-pages`.
-It will get merged into the latter when released as stable.
+Everyone is invited to participate in the Leaflet community and related projects:
+we want to create a welcoming and friendly environment.
+Harassment of participants or other unethical and unprofessional behavior will not be tolerated in our spaces.
+The [Contributor Covenant](http://contributor-covenant.org/version/1/3/0/)
+applies to all projects under the Leaflet organization.
+Report any issues to [email protected].
 
 ## Thank You
 
-Not only are we grateful for any contributions, &mdash; helping Leaflet and its community actually makes you AWESOME.
+Not only does your contribution to Leaflet and its community earn our gratitude, but it also makes you AWESOME.
 Join [this approved list of awesome people](https://github.com/Leaflet/Leaflet/graphs/contributors)
 and help us push the limits of what's possible with online maps!

FAQ.md

@@ -26,12 +26,11 @@ You can roll your own tiles as well.
 but there are providers that use other sources.
 
 Check out [this example](http://leaflet-extras.github.io/leaflet-providers/preview/)
-with half a hundred different layers to choose from.
+with over seventy different layers to choose from.
 Popular commercial options, free up to a particular number of requests, include
 [MapBox](http://mapbox.com),
-[CloudMade](http://cloudmade.com),
-[Bing Maps](http://www.microsoft.com/maps/choose-your-binge's-maps-API.aspx) (using a [plugin](https://github.com/shramov/leaflet-plugins)),
-[Esri ArcGIS](http://www.arcgis.com/features/maps/imagery.html) ([official plugin](https://github.com/Esri/esri-leaflet))
+[Bing Maps](http://www.microsoft.com/maps/choose-your-bing-maps-API.aspx) (using a [plugin](https://github.com/shramov/leaflet-plugins)),
+[Esri ArcGIS](http://www.esri.com/software/arcgis/arcgisonline/maps/maps-and-map-layers) ([official plugin](https://github.com/Esri/esri-leaflet))
 and [Nokia Here](http://developer.here.com/web-experiences).
 A notable exception is [MapQuest Open](http://developer.mapquest.com/web/products/open/map), which is free for any number of requests.
 
@@ -41,12 +40,12 @@ Always be sure to **read the terms of use** of a chosen tile provider, **know it
 
 [MapBox](http://mapbox.com),
 [Bing Maps](http://www.microsoft.com/maps/choose-your-bing-maps-API.aspx),
-[ArcGIS](http://www.arcgis.com/features/maps/imagery.html)
+[ArcGIS](http://www.esri.com/software/arcgis/arcgisonline/maps/maps-and-map-layers)
 and [MapQuest Open](http://developer.mapquest.com/web/products/open/map) provide satellite imagery among others.
 
 #### I want to use Google Maps API tiles with Leaflet, can I do that?
 
-The problem with Google is that its [Terms of Use](https://developers.google.com/maps/terms?hl=ru) forbid any means of tile access other than through the Google Maps API.
+The problem with Google is that its [Terms of Use](https://developers.google.com/maps/terms) forbid any means of tile access other than through the Google Maps API.
 
 You can add the Google Maps API as a Leaflet layer with a [plugin](https://github.com/shramov/leaflet-plugins). But note that the map experience will not be perfect, because Leaflet will just act as a proxy to the Google Maps JS engine, so you won't get all the performance and usability benefits of using Leaflet when the Google layer is on.
 
@@ -86,6 +85,10 @@ Make sure you conform to the terms of use of the tile images provider(s) that yo
 
 ## Features
 
+#### What's the best way to put the data I have on a Leaflet map?
+
+Check out [this awesome cheatsheet](https://github.com/tmcw/mapmakers-cheatsheet).
+
 #### Why is there still no feature X in Leaflet?
 
 First of all, did you check out the [Leaflet plugins page](http://leafletjs.com/plugins.html)?

Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gem 'github-pages'