Open tahini opened 8 hours ago
Can we quantize the benefits of going individual stuff?
Can we quantize the benefits of going individual stuff?
Not exactly, as I'm not sure how many less packages will be required if we do so. But lower bound: turf-jsts
which is used by @turf/buffer
which is not used by us takes 5% of the build space in the survey bundle (after reduction of some obvious packages that were taking a lot of space in the survey bundle).
At some point, it was decided to import required functions from @turf/turf, to make sure we only have one version of
turf
to deal with.But it turns out the the whole @turf/turf is imported in the webpack bundle, even with webpack's tree shaking activated.
Though @turf/turf is a facade for all turf packages, we cannot import individual packages like
@turf/distance
for example, as we get a linter errorerror "@turf/distance" is extraneous n/no-extraneous-import
To investigate