ESM build has classes downleveled to functions, but CJS build does not about js-sdsl HOT 3 OPEN

Yes, We hope that Js-sdsl can be compatible with more browsers so we set target to ES5 for ES module.

from js-sdsl.

All modern browsers support much higher than es5 though - esp if they truly support ESM.
For example every modern browser supports es6 classes https://caniuse.com/es6-class

Why not just leave it to the user to downlevel your code for their target environment? It's going to be very, very rare that anyone is going to consume your package on the web without passing it through a bundler first.

The issue is that anyone consuming your package from nodejs is stuck using your downleveled code if they import your package via ESM - which is a really backwards experience!

from js-sdsl.

All modern browsers support much higher than es5 though - esp if they truly support ESM. For example every modern browser supports es6 classes https://caniuse.com/es6-class

Why not just leave it to the user to downlevel your code for their target environment? It's going to be very, very rare that anyone is going to consume your package on the web without passing it through a bundler first.

The issue is that anyone consuming your package from nodejs is stuck using your downleveled code if they import your package via ESM - which is a really backwards experience!

Sounds good, we might change the building target of ESM to ES6 at version 5.0.

from js-sdsl.