In theory dependencies shouldn't matter, because normally only your own code goes through Babel; library code has typically already been transformed into least-

In theory dependencies shouldn't matter, because normally only your own code goes through Babel; library code has typically already been transformed into least-common-denominator JavaScript Most of these are pretty hard to do by accident... I didn't even know about maybe a third of these things, and I've been writing JavaScript for 10 years A significant exception to all of the generalizations I've been making is iterableIsArray: > When using an iterable object (in array destructuring, for-of or spreads), assume that it is an array. Violating this one is neither an anti-pattern nor hard to do by accident. It would mean a significant shift in practices for a project, and it would have to allow for some really exceptional optimizations if I were going to even consider enabling it