jonschlinkert / remarkable / 799

99%

dev: 99%

push

travis-ci

Use named exports for public api (#354)

Default exports are always a headache for public api. They are hard to
use when same module is used for both node and webpack via commonjs.
We have this problem

https://github.com/webpack/webpack/issues/6584

Mixing named and default exports works even buggier.

https://github.com/webpack/webpack/issues/7973

The best solution is using only named exports. They fits perfectly with
interops and may work without interop for commonjs.

(module.exports = was a mistake, export default IMO too)

1309 of 1413 branches covered (92.64%)

2235 of 2268 relevant lines covered (98.54%)

1175.24 hits per line