Closed edg2s closed 4 years ago
Does this effectively change our eslint compatibility? With this, we're now increasing our required node level above what eslint 2 requires, I think?
Hopefully not as we were already using Array.includes...
Also we only claim to support ESLint 2.3, not the lowest version of Node that that supports. You can use 2.3 with Node 14...
Array.includes requires Node 6, but so does Object.assign, and probably a bunch of our dependencies.
WFM. Maybe we can put the engine requirement in package.json for clarity?
Codecov Report
100.00% <ø> (ø)
100.00% <ø> (ø)
100.00% <ø> (ø)
100.00% <100.00%> (ø)
100.00% <100.00%> (ø)