Major release pre-announcement (TurfJS v5.0)
See original GitHub issueMajor release pre-announcement (TurfJS v5.0) ⭐️ 📢
Due to some drastic changes coming up, the next TurfJS release will be v5.0
(Major release).
If anyone has any suggestions for breaking changes, the time would be now to do it.
Timeline
Approximately a 1-2 weeks (end of September/ early October, 2017).
Major To-Dos before publish
- Finish adding new optional parameters (
options
) (PR https://github.com/Turfjs/turf/pull/953) - Convert to ES6 modules using Rollup (PR https://github.com/Turfjs/turf/pull/960)
- v5.0 issues
Not happening for next publish
-
jsts
won’t be entirely removed
@stebogit @rowanwins Any additional suggestions for v5.0
changes?
Don’t hesitate to send some breaking PR changes (within reason & approved).
Issue Analytics
- State:
- Created 6 years ago
- Comments:25 (16 by maintainers)
Top Results From Across the Web
Advanced geospatial analysis - Turf.js
Takes a GeoJSON object and returns a simplified version. Internally uses simplify-js to perform simplification using the Ramer-Douglas-Peucker algorithm.
Read more >A modular geospatial engine written in JavaScript - JsRepos
Major release pre-announcement (TurfJS v5.0) ⭐️. Due to some drastic changes coming up, the next TurfJS release will be v5.0 (Major ...
Read more >@turf/turf - npm
Latest version: 6.5.0, last published: a year ago. ... It is maintained in the Turfjs/turf repository, where you can create PRs and issues....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
JSTS - the undead legacy library ported from lovely Java 4 (!) compatible code that just… wont… die. 😈
Monkey is about keeping API compatibility with previous version and upstream but are really only delegates from Geometry to other modules. Was broken out into a hacky money patch because it creates evil circular dependencies. Would like to see it removed in the future but depends on upstream.
The monkey patch can be avoided entirely, but it’s not clearly documented yet (although can be found in API docs). I made this example yesterday http://bjornharrtell.github.io/jsts/index_modules.html that might shed some light…