Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Drop support for Node v4

See original GitHub issue

Description

Node will drop maintenance for v4 in April 2018 so I think we’re pretty safe on dropping it now since I believe most of our users are early adopters either way. Supporting Node v4 right now is coming to an unwanted chores like in #367 or in #371.

Migration path

Introduce a breaking change with a major version bump that only changes engines field in the package.json + updates Travis config.

Issue Analytics

State:
Created 6 years ago
Reactions:3
Comments:32 (14 by maintainers)

Top GitHub Comments

3reactions

okonetcommented, Jan 31, 2018

@sudo-suhas no I honestly I don’t want to start using it—the syntax is weird IMO.

My conclusion is still the same: I don’t want to please everyone, especially when doing this for free. So if the 25% of users will have to stick to the older version because of that, I’m okay with that. They also can upgrade to Node 8, which is a win-win for everyone.

So I’m voting for dropping Node 4 and going straight Node 8.

2reactions

okonetcommented, Jan 30, 2018

Since lint-staged is meant to be used only during development, I’m not sure if AWS support should be considered as an issue…