package-lock seems to be redundant

Recently I've seen it become more common to ensure the deps exactly match w/ a successful build. If it's not required for this then that's fine.

@async0x42 I prefer keep libraries up to date, because when some deps becomes making troubles, it is two possible ways to choose:

1. froze last properly worked version
2. update our code to be up to date

@async0x42 Thank you for PL ;)

@async0x42 I prefer keep libraries up to date, because when some deps becomes making troubles, it is two possible ways to choose:

1. froze last properly worked version
2. update our code to be up to date

It's what I do for my private repos; works for me!

@async0x42 have You any idea how fix travis check for node v6?

@async0x42 have You any idea how fix travis check for node v6?

Off-hand, I don't to be honest, and I won't have time to dig into it for a little while. Node v6 will be EOL itself in ~2 months (April 2019), would it be OK to just drop support for that a little early?

Ref: https://github.com/nodejs/Release

Should we merge this on 1st of May, when node 6 is no longer supported? :)

@alubbe @guyonroche , so, v6 is EOL, we should update our Travis.

unfortunately, we do not test v11 and v12, should we?

#803