Drop Node.js 4 & other housekeeping chores #1760
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're only a few weeks away from Node.js 4 reaching end-of-life. It's likely that Babel 7 will drop support, and it's also quite likely we won't ship the non-beta 1.0 release until after the cut-off. Consequently let's drop Node.js 4 now, rather than next month.
I've amended the support statement to allow for this circumstance:
Let's hold off on aggressively rewriting code until the big 1.0 work completes.
Housekeeping wise I've upgraded npm to 5.8.0 so we can utilize the
npm ci
command. I'm still verifying thepackage-lock.json
matches what npm in our CI environment generates, but thelock-verify
step has been removed from ourlint
command.Most dependencies have been updated, including TypeScript and Flow.
I'm going to land this once CI passes, so I can rebase #1722 and land that one too. Happy to make changes in response to feedback in a follow-up PR.