Name collision with JS BigInt

[littledan]

Now that JavaScript has BigInt as part of its standard library, I'm a little concerned that people might stumble upon this module in npm and use it when they are trying to get at standard BigInt. What do you think we should do? cc @zkat

[littledan]

See https://github.com/tc39/proposal-bigint/ for more information.

[zkat]

@littledan I think it's best to leave the module authors to make decisions about documenting/compensating for it, as they should for any shim. You might consider sending a PR to this repo, just leaving this issue so they know, etc. Keep in mind that even when BigInt becomes standard, people will be using useragents that don't support it for years to come, after all :)

Anyway, tl;dr, leave it to the commons itself to figure this one out.