v7 alpha release

Inline with the suggestions contained within #1428 I’ve been working on getting a v7 release ready (see #1432)

API Changes

• There haven’t been any changes to module API’s

Higher level changes

• Modules are now ES6 modules, written in plain ol’ js, and built into a single package using rollup
• Lerna is now no longer used for publishing as only a single package is published

Module enhancements

• JSTS has been replaced in union, difference, intersect by polygon-clipping -dissolve has been overhauled
• a number of other minor enhancements and fixes to modules…

Testing

• My initial testing of the alpha bundle has been going ok
• @shongololo has raised an issue around ReferenceError: m is not defined when buffering linestrings.
  • need to do a bit of digging here, may be a minification issue or something else… although see note below, ideally I’m hoping to do away with the jsts dependency in the buffer module

Outstanding issues

• The only module where jsts remains in use is buffer. I’m currently working on a replacement here
• In the buffer replacement above I’m trying to build my library pulling in a couple of turf modules (eg coordEach). For some reason the build is pulling in all of turf rather than just the couple of modules I want (aka tree-shaking doesn’t appear to be working…)
  • In my case I’m again using rollup as my build tool. I could perhaps investigate using webpack although it would be nice to have turf ‘just working’ irrespective of build tool choice.

Where to find it

• v7.0.0-alpha.1 has been published to npm
• Or it can be found in the v7 branch

What next

• Try to resolve tree-shaking issue noted above
• Publicise changes more widely

cc @stebogit @tmcw

[rowanwins]

Hi @zakjan & @dpmcmlxxvi

There are a few more unresolved issues around the polygon-clipping library that are preventing it from shaking properly, for example I think this use of the singleton pattern, as well as these variables and functions. I have a version locally which shakes however it breaks a lot of tests which would need to be refactored accordingly.

With tree-shaking I think the meta and helper modules these will be relatively low priority as minified they come out very small.

I’ve also released point-in-polygon-hao recently which works with polygons containing holes out of the box as well as degenerate polygons (compared to point-in-polygon).

[sheerun]

Our application size is suffering from jsts. Maybe some help rewriting buffer? Could you point to something?