Jarvis does not compile without 'use strict'; in older node versions about jarvis HOT 7 CLOSED

reference https://nodesource.com/node-by-numbers ，but actually i think set Node 6 the minimum supported version is good . Node develop very fast ,too hard to compatible

from jarvis.

I think I will set the engine in package.json to support node 6 as a minimum!

That will help us build & ship faster too!

from jarvis.

I may be wrong, but I think Node 6 is meant to be the minimum supported version on purpose. We should add that to the engines key if that's the case.

from jarvis.

We actually have not tested this on pre-node 6!

Do we know how big is the user base still on Node 4.x and 5.x? :(

from jarvis.

Webpack seems to support Node versions older than 6(at least as of now). Will setting Node 6 as minimum requirement for JARVIS make it unusable for webpack users who're still on older versions of Node?

Quite not sure if it matters and I know it's going to be really hard to keep up the compatibility. I thought I'll just bounce this off.

from jarvis.

it's already unusable, because it will break, this way they get a warning ahead of time

Don't see the point in supporting anything older, node 4 is in maintenance and will be dropped in april, if you're still using anything < 6 you should upgrade ( to 8 )

from jarvis.

I think this issue is done.
packageJson engines

from jarvis.