Help me identify which forks/PRs are worth merging

[kadamwhite]

Hey all! I'm an old colleague of @mzgoddard's, and he was kind enough to grant me maintainer rights on this repo to help clean up some of the backlog. Unfortunately I'm juggling a lot of projects, and do not have the time or background to thoroughly triage the issues and PRs open here.

Asking for help: If we can get consensus about which PRs or forks are commonly in use to work around issues, that'll give me the clarity I need to test and merge / release those PRs in the time I have available.

I'm also looking for other folks who have been iterating on this code who would be interested in helping to maintain it to clear out the issue backlog.

Thanks, 🙏

[ansballard]

Evening! I had a look into #416 and the associated PR: #497. As far as I can tell, it's safe to merge. It's already being used in a separate npm package (2k weekly downloads), and the travis errors are the same as all the other PRs. I put a little more detail in a comment on the PR as well.