build: use tsc output code in both cjs and esm formats

[Lxxyx]

Fixes: #126

[Skn0tt]

Thanks @Lxxyx for this PR! After looking at the build output of TSDX, I have two questions:

1. is it possible to not bundle the output together? Bundling should be the responsibility of final application build, and having an unbundled output makes debugging easier for us.
2. It currently outputs declaration files for each of our source files, allowing people to import superjson/accessDeep or smth. But since the javascript code for that is all in the bundles, that import will break. Is there a way to omit these per-file declaration maps / have them bundled together?

I tried to look them up in the TSDX docs, but couldn't find anything. Maybe you have an idea :D

Also: Do you think it'd be possible to add ESM support without using TSDX? One of the reasons I removed it in #97 is that it does a whole lot of things that I don't understand, and I didn't see the benefits for a small library like SuperJSON.

[Lxxyx]

@Skn0tt We can do this. Use tsc to output code in both cjs and esm formats, and be forward compatible

{
  "scripts": {
    "build": "npm run build:cjs && npm run build:esm",
    "build:cjs": "tsc",
    "build:esm": "tsc --module es2015 --outDir dist/esm"
  },
  "module": "dist/esm/index.js"
}

[Skn0tt]

We can do this. Use tsc to output code in both cjs and esm formats, and be forward compatible

That'd be great!

[Skn0tt]

LGTM! Thanks a lot for your work on this ❤️

[Skn0tt]

Published in v1.7.3

[Skn0tt]

@allcontributors add Lxxyx for code

[allcontributors]

@Skn0tt

I've put up a pull request to add @Lxxyx! 🎉