Poll: Minimum Node Support

[lukeed]

With beta, I bumped up minimum Node support to 4.6 because it was an LTS release. However, now active 4.6 LTS is ending in April. And since beta development took a bit longer than expected (IRL, sorry), April isn't very far away.

Poll: Should we continue to stick to 4.6 or bump the minimum version to 6.9 before April?

In addition to LTS coverage, with 6.9 we also get:

• default function parameters
• rest parameters
• spread operator
• destructuring declarations
• destructuring assignments
• destructuring parameters

Reaction response:

• 👍 for 6.9
• 👎 for 4.6

Please only comment if you've cast a "reaction" vote.

---

cc/ @jbucaran @hzlmn @devmondo @Akkuma @tjbenton @watilde @frantic1048 @aweary @pine

[lukeed]

Everyone seems to be onboard with the change. Should we just upgrade to 6.9 now? 🤔

[hzlmn]

I think yes, but we need to check depedencies for proper support of 6.9.

[lukeed]

@hzlmn Cool. They all do. I've been running on 6.9 & Fly for a while now.

[lukeed]

As of 2.0.10-beta, Fly now requires Node 6.x.

[lukeed]

Version 2.0.2 continues support for Node 4. This will be revisited in April once LTS has officially expired.

[Swizz]

Do all plugins, need to follow this Node4 support ?
And what about plugins that uses dependencies that not meet this support ?

Should I use transpiling at runtime to ensure the support ?
Or may I use the engines field (and doc warning) to locked the support ?
To the 6 LTS version or the minimal supported one ?

I know I am a lit bit annoying, but I fallen in love about Fly, and want to do my best.

[lukeed]

Lol not annoying at all!

It's entirely up to you since you're the plugin author. However, it would be better for the user to assume that everything will work within the ecosystem.

Obviously, you can't control that in some cases (third-parties). But most existing tools out there are still supporting Node 4 because it is officially still supported. That is why we've reverted to 4.x support.