CJS export is missing __esModule - Code transpiled to CJS can't use default export

[agilgur5]

See #3 (comment) onward.

This is a bug in tsdx (jaredpalmer/tsdx#165) caused by caused by this config option in its rollup config

This bug makes the v0.1.0 release unintentionally breaking (to an extent at least, as CJS support wasn't available before v0.1.0) and as such fixing it should be high prio. The workaround is to not use default exports, but default is used in the README and v0.1.0 should maintain backward compatibility (though minor releases prior to v1 are allowed to be breaking, this was unintentionally breaking)

[agilgur5]

Oh wait... default export actually isn't listed in the README. I have used it in code blocks when responding to people though and believe I went back-and-forth on whether to use default in the README or not. Guess it's a good thing I didn't given there are more issues with it than I knew of.

Still breaks backward compatibility and is an unexpected bug in tsdx, but not that high prio given it's not in the README and has a workaround available.

[agilgur5]

Sent a PR out to tsdx to fix this: jaredpalmer/tsdx#327 .

Tried a simpler/quicker fix back in July, but that failed upon testing. Decided to try a different fix after some renewed frustrations as a result of that bug and that PR does indeed work now!

[agilgur5]

Would like to release the fix to this in v0.1.x so that it's fixed in the same minor it was broken and is fixed in all future minors.

That would mean before #16 lands as it'll be a minor release. If jaredpalmer/tsdx#327 isn't merged and released soon, I've created a branch on my fork at agilgur5/tsdx#dist that has the change and is installable via npm i -D tsdx@github:agilgur5/tsdx#dist. It can be used in the meantime then.