Updates Travis CI and packages

[striezel]

Node.js versions below 10.x are not maintained anymore, so it is probably best to use some newer, still maintained versions. For release cycles of Node.js see the official site: https://nodejs.org/en/about/releases/.

Furthermore, the Mocha dependency has been updated to use the most recent version, fixing several vulnerabilities along the way.
Despite several major version bumps the tests still run. :)

[striezel]

@bryanburgers:
No response for almost two months. Is there anything missing to get the pull request merged? If that is the case, then please let me know and I will try to fix that.

[tmcw]

I contributed a PR to this project in 2016. I'm not the maintainer of this project and don't have push rights. Can you be a little more careful in who you spam with notifications?

[striezel]

I contributed a PR to this project in 2016. I'm not the maintainer of this project and don't have push rights. Can you be a little more careful in who you spam with notifications?

Sorry about that, my mistake. Should not happen again.

[striezel]

@bryanburgers: Is there a chance that this PR gets reviewed or gets any feedback? I would appreciate that, even if it is just a "I'm not interested in those contributions."

[bryanburgers]

Nope. I have no interest in this package. What’s the next best option? I’m willing to transfer ownership of the project if that’s the best next option.

[striezel]

Nope. I have no interest in this package. What’s the next best option?

The next best option is probably to find a new maintainer for that package then. That means someone who is willing to maintain the package and who you trust to be a good maintainer. To be clear: I do not want to be the maintainer or owner of this project. I just came here to get an update in.

I am not sure whether a new maintainer would need ownership of the project or whether it is enough to give the maintainer the rights to merge, commit and push to this repository. But a new maintainer would also need the permission to publish potential newer version of this package to npmjs.com.

If no new maintainer can be found, another option would be to clearly mark this package as deprecated / abandoned / not maintained anymore, e. g. by placing a corresponding notice in a promiment place like the top of the readme, and then archiving this repository. Obviously, this is not the preferred option, but it would clearly indicate the current state of the project.