[MarkusWendorf]

I noticed that root imports from ramda pull the whole library into the bundle. This is not an issue if you have tree-shaking enabled, however by default Expo/Metro based projects do not have tree shaking enabled.

EXPO_UNSTABLE_TREE_SHAKING=1 can be used to enable it, but is marked as unstable for now.

This PR changes to deep imports via import x from 'ramda/src/x instead of barrel imports.

I setup some tests to see the difference. Not quite sure if import x from 'ramda/src/x or import x from 'ramda/es/x is the best way to go.

If this is ok to be merged, maybe adding an ESLINT rule for imports would make sense. Let me know.

AI summary ahead ↓

Production app

Expo SDK 58, React Native 0.88, Android, Hermes bytecode.

Import style	Tree shaking	Hermes bundle	gzip	ramda in bundle
import { x } from 'ramda' (current)	off	10,095 KB	4,107 KB	129 KB / 367 files
import x from 'ramda/src/x'	off	9,845 KB (−250 KB, −2.5%)	4,045 KB (−1.5%)	10 KB / 46 files
import { x } from 'ramda' (current)	on	8,717 KB	3,564 KB	15.8 KB / 47 files
import x from 'ramda/src/x'	on	8,705 KB (−13 KB, −0.15%)	3,563 KB	10 KB / 46 files

The Hermes bundle column is the shipped bytecode; ramda's size comes from the minified-JS source map. Tree shaking is Expo's
experimental mode (EXPO_UNSTABLE_TREE_SHAKING=1 + EXPO_UNSTABLE_METRO_OPTIMIZE_GRAPH=1).

Example app (already has tree shaking enabled)

apps/benchmarking (Android, minified JS). The app's own import { mean } from 'ramda' in Benchmark.js was replaced with a
local helper so only the library is measured.

Import style	Tree shaking	Bundle	gzip	ramda in bundle
import { x } from 'ramda' (current)	on	2,471 KB	631 KB	16 KB / 47 files
import x from 'ramda/src/x'	on	2,461 KB (−0.4%)	631 KB	10 KB / 46 files
import x from 'ramda/es/x'	on	2,470 KB	631 KB	15 KB / 46 files

[5ZYSZ3K]

Recently there was an issue proposing the exact opposite: #49
It made more sense to me to leave it for tree-shaking to decide, which chunks of code to keep

However I need to admit I didn't do a throughout research, I just run one agent to confirm and fix the issue
I'll assess that better this time

[MarkusWendorf]

@5ZYSZ3K haha, that's interesting. I asked the creator of said issue to provide details so we know why tree-shaking was not working for him.