Denis

👍 that wouldn't be a bad idea. However then it wouldn't look as "clean" & simplistic as => ```json "scripts": { "test": "xo && ava" }, ```

ES6 generators 👍 As for making it backwards compatible, we can simply use Babel to compile down the code to IE11 compatible. If we decide to go towards the generator...

I'm thinking it might be a Google Maps projection (Leaflet would be the same). 🤔 Not too sure.

@bulutkartal Feel free to send a PR with an option for mercator. 👍

@bulutkartal send a PR with your test case to [packages/turf-point-on-line/test.js](https://github.com/Turfjs/turf/tree/master/packages/turf-point-on-line/test.js)

> I've never done this before. Better late then never right? 😄 GitHub has tons of documentation to get you started, here's one that might help you start: https://help.github.com/articles/fork-a-repo/

👍 Support having elevation in all computations, reference https://github.com/Turfjs/turf/issues/628.

@rowanwins I had to refactor `simplepolygon` and I internalized the library into Turf to get the build to pass. Maybe it was something in the refactoring? https://github.com/Turfjs/turf/blob/master/packages/turf-unkink-polygon/lib/simplepolygon.js https://github.com/Turfjs/turf/blob/master/packages/turf-unkink-polygon/lib/geojson-polygon-self-intersections.js Might be...

👍 Just confirmed that this is a bug 🐛 I'll send a PR with the test case included, we can investigate this more on the PR.

@rowanwins Darn... 🤕 I tried replacing `simplepolygon` with the upstream npm version and it still didn't fix the issue... at least it's not the refactored code the issue.