/es package entry point is conventional in modern libraries.
The suggestion is to provide rambda/es imports in ES5 and ES module format , similarly to how it was done with ramda/es. Notice that Ramda modules are transpiled to ES5 to skip transpilation on bundling, and there is index reimporting file.
The package has rambda/lib which is CJS. It doesn't have index (there will be problems with tree-shaking any way) and requires to use module interop when imported as ES modules, this results in increased footprint.
/es
package entry point is conventional in modern libraries.The suggestion is to provide
rambda/es
imports in ES5 and ES module format , similarly to how it was done withramda/es
. Notice that Ramda modules are transpiled to ES5 to skip transpilation on bundling, and there is index reimporting file.The package has
rambda/lib
which is CJS. It doesn't have index (there will be problems with tree-shaking any way) and requires to use module interop when imported as ES modules, this results in increased footprint.