Allow 3.0 to be backwards compatible with < Node 8

[darkguy2008]

Allow 3.0 to be backwards compatible with < Node 8

[pik]

@darkguy2008 Thanks! It may seem uncommon in the JS ecosystem but e.g. with Python checking version is a pretty common way to make a single code-base / library compatible with both Python versions. I could provide a quick-patch if it's desired.

[darkguy2008]

Hi all, sorry for the delay, I've been really busy with work but I got a notification here and set up some time to test and tidy up the repo a little bit. The PR has been merged, I need to update the packages and whatnot now 👍 thanks @pik !

[darkguy2008]

Hello!

I see, well, the < 2.1 version does work with < Node8, and 3.0+ with >= Node8, but then again you do have a point and it seems to be a small fix, although I don't like much to create a dependency by checking the runner's version inside a library, it's useful for node < 8 users.

I'm sorry I didn't add this before, I will do it right away. Thanks for your concern! 👍

[darkguy2008]

@pik thanks for your insights, it makes sense now :). I've been a bit full these days and from what I could see, the variable should be process.versions.node... I could check if process.versions.node[0] == '8' but I'm not sure if that's okay... I'd need some time to set up different node envs to try. If you are able to make a patch, I'll happily review it and apply it immediately, what do you think? :D

[t3chguy]

@darkguy2008 @pik made a patch

[Nostradamos]

Did anyone try to contact @darkguy2008 on other channels (eg his email)?
Would love to see this PR merged.