Mateusz Burzyński
Mateusz Burzyński
As explained [here](https://github.com/ramda/ramda/issues/1505#issuecomment-340285426) first three options you have presented are basically **the same** - they do exactly the same thing. Please follow related discussions (they should all be linked in...
Both "jsxnext:main" and "module" have nothing to do with `babel`. `Babel` is just a transpiler and it doesn't resolve your modules, it operates on single files only. Those fields are...
So the case is closed, right? Please remember about closing the issue on ramda-adjunct board 😃 Cheers!
When i've optimized this stuff the lib became almost fully tree-shakeable when importing stuff from the root entrypoint. This was quite some time ago - cant say if there were...
Yes, when I was testing this out this was sufficient to get almost perfect tree-shaking - there was no need to use deep imports like `ramda/es/add` etc
Well, hard to say what's going on if you don't share **full** repro case that could be inspected and analyzed.
If you were using some bundle analyzer here - then it's broken. IIRC some of those were just hooked into webpack **before** certain optimizations were executed so they were always...
@CrossEye it really isnt worth it 😂
:facepalm: I would probably try this: ```json "./es/*": "./es/*.js", "./src/*": "./src/*.js", "./dist/*": "./dist/*.js", "./es/": "./es/", "./src/": "./src/", "./dist/": "./dist/" ``` Note that I didn't test this but I don't see...
@barleendhaliwal I'm not a project maintainer here... but I feel somewhat confidently saying that "PRs are welcome" 😉