Suggesting curators and CDN of most used Turf methods

Hi, can I suggest here an issue for CDN users? Something as “Popular Turf modules CDN”, a Turf subset of most frequently used Turf modules.

The standard CDN for turf.min.js is a ~600kb file, so big for some applications… But ~300kb or less file is not so big… There are many Github, GitLab, etc. projects that use only a little subset of Turf… And supposed that is possible to build a commom subset that will be a suitable CDN for 50% of more of them.

Curatory statistcs: the curators need only to list a set of use cases (example), with lines of import _module_ from '@turf/_module_' …

PS: another good starting point will be a statistics of a turf-builder.

[stebogit]

It look like on jsDelivr you can link any specific file inside a GitHub project.

I wouldn’t create a separate project, but I do like the idea of a “Truf-light” or “Turf-essentials”. We could simply build a production file for a subset of modules and define (i.e. officialize) new CDN links. We could even define other specific subset packages like, for instance, “Turf-transform” with the transform modules (and maybe some useful related ones, if that makes sense) for polygon transformation.

[morganherlocker]

@ppKrauss This is a good suggestion, but not something we have bandwidth to support. Custom builds are possible to generate with well maintained tools outside Turf, which is the standard level of distribution support provided by most modules. This allows you to mix and match Turf modules however works best for you, providing maximum flexibility.

@ppKrauss well I don’t know either how exactly the .min files are created 😅

We have traditionally used the uglify module for generating minified distributions. Combined with browserify, you can create any type of distribution you need by following the docs on those tools.