Compatibility checker about electionguard-typescript

[danwallach]

And, in fact, there are a bunch of great property detectors in the stdlib project. These are exactly what we need.

https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/assert

[shreyasminocha]

I was thinking about doing all the checks in index.ts and throwing an error if something was missing. Does that also work or is the "a function that" part necessary?

Related also: We're currently building commonjs modules, which likely wouldn't work in browsers. We could set up a separate browser build, or we could try to build es6 modules, which should work in both node and browsers. The only blocker for that should be seedrandom's lack of esm module support, which I think can be fixed by replacing it with esm-seedrandom? Ugh. Nevermind, I got this part working, but I'm still unsure if the es6 modules tsc is generating will work as-is in browsers. #27

The other consideration with browsers, though, is that we probably want to output a single js file that includes everything? AFAIK tsc doesn't let us do that, so we'll have to bring in rollup or webpack or something.

[danwallach]

Found this:
https://github.com/Modernizr/Modernizr

Unsurprisingly, there's a library that knows how to do most of the work we need.

Lets move the webpack/commonjs discussion to a separate issue. The point of this issue is just having some code in front whose job it is to fail fast if we're on an antiquated platform. Maybe this check occurs inside the GroupContext fetcher?

[danwallach]

Also: https://featurejs.com/

This can detect async, which is good, but neither this nor Modernizr seem to have bigint detection.

[danwallach]

But this has exactly what we need for bigint:
https://github.com/stdlib-js/assert-has-bigint-support