For additional context: Is this about tests running within node's CI, locally, or for travis (or all of them). Asking because "have some kind of CI" is still an open issue for this repo. :(

@jkrems Locally. I thought we had resolved the Travis issue for this org, for the most part? I’ll try to check.

Last time I tried to fix Travis, there seemed to be some builds but they didn’t report to the PRs. I suspect that “delete project on Travis, try from scratch” would be a best strategy at this point.

Maybe switch to GitHub actions for testing?

Maybe switch to GitHub actions for testing?

I've opened a PR to add testing with GitHub Actions: #78
It looks like tests are broken with tap 14 -- I've dropped back to tap 12 in that PR and tests are passing on Node.js 12 and 13 but failing on 10.

It may be worth it to bump the major version and set the minimum version to 12. I don't think we'd back-port node inspect changes to node 10 given how infrequent these were in general.

I'm planning to merge this PR soon since it seems like it brings us closer to stable. Please protest if that doesn't work for people. :)

I don't think it's necessary to revert the eslint and lint changes but won't stand in the way of this land (those can always be landed again separately without the tap upgrade after the revert).