Use standard `exports` in `package.json` about tslib HOT 3 CLOSED

webpack and other bundlers use it - it's for scenarios where the bundler ensures esm and cjs are drop-in replacements for one another, so only loads one copy of a module (the module version), unlike node, which loads two (the require and import version), and we need to take steps to ensure only one copy of the code is loaded (but still presents the right named exports).

It's entirely "standard" in that regard.

from tslib.

FYI, the node docs page for conditions here may not list module, but it 100% meets the bar for inclusion (it's well supported by a tool in the ecosystem already and a bunch of packages use it, not just tslib) - nobody's added it yet though because it's just an as-requested thing.

from tslib.

Ok, thanks for the explanation

from tslib.