You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now consider this one-liner (run with node --harmony):
new Set([1,2]).forEach(function(item) { console.log(item); });
It outputs nothing. That's a bug in V8, because according to ES6 draft it should list the items.
This breaks both projects which rely on the correct behavior OR which rely on the absence of Set.prototype.forEach (till recent times in V8).
For me, it triggered a failure within a module array-uniq using new Set, and this module was used by array-union, then multimatch, then gulp-load-plugins then my build system.
I believe it can cause other problems as well for other people.
Installed node 0.11.14 on MacOs.
Now consider this one-liner (run with
node --harmony):It outputs nothing. That's a bug in V8, because according to ES6 draft it should list the items.
This breaks both projects which rely on the correct behavior OR which rely on the absence of
Set.prototype.forEach(till recent times in V8).For me, it triggered a failure within a module
array-uniqusingnew Set, and this module was used byarray-union, thenmultimatch, thengulp-load-pluginsthen my build system.I believe it can cause other problems as well for other people.