Move to Node 8

[bmuenzenmeyer]

Dropping 6 in favor of 8 will move with the Node LTS "Active" schedule, the industry as a whole, and allow us to use newer language features like async / await

• nvmrcs
• travis environments
• package.json engines
• documentation / README / shields

[EvanLovely]

Love this. Gotta say: async / await is super handy & much more readable than other approaches.

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[benhalverson]

Hey @bmuenzenmeyer Do you mind if I work on this?

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[stale]

Issue closed after going stale. It can be re-opened if still relevant.

[sghoweri]

Reopening — my gut tells me that this should be pretty straight forward to bang out the minimum updates needed for this (aka we could upgrade to Node 8 but hold off refactoring any logic to use async/await till a later batch of updates).

[bradfrost]

@sghoweri That sounds good. I wouldn't trust me to do that upgrade, but in any case I'd hope the universe doesn't blow up by upgrading.

[benhalverson]

@sghoweri @bradfrost This is already done see #951 and #951 (comment) about going to node 10 instead of 8

[bradfrost]

@benhalverson ah thanks for the heads up. @sghoweri does this sort you out?

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[sghoweri]

Closing this out. Going with Node >=10 sounds great to me (lots of optimizations we’ll be able to get in) and the updates bumping the min version needed (#951) shipped with the latest beta we cut last week!