update travis to test on supported versions of Node.js

[Trott]

No description provided.

[zkat]

This is gonna have to be a breaking change, and I think it's fine to merge when we next do a run through all our dependencies for a following release of npm itself.

[Trott]

I think it's fine to merge when we next do a run through all our dependencies for a following release of npm itself.

@zkat Is there a way for me to know when that is likely to happen or not really?

[tniessen]

There have been at least two semver-minor releases, maybe npm is waiting for a semver-major release? #6 isn't even a breaking change and has received literally zero attention over the past six months... npm audit also complains about this module, it appears to be unmaintained.

[Trott]

There have been at least two semver-minor releases, maybe npm is waiting for a semver-major release? #6 isn't even a breaking change and has received literally zero attention over the past six months... npm audit also complains about this module, it appears to be unmaintained.

I understand your frustration. FWIW, I'm pretty sympathetic to npm on this. They have a very small team and updating .travis.yml on this specific module just isn't going to be a priority for them compared to fixing bugs in the cli, adding features to the cli, and addressing whatever security/stability issue might be lurking out there that we don't even know about.

All that said, if there's something I can do to get stuff moving in this repo, I'd love to. I'm guessing they don't hand out the commit bit lightly, though.