New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babel loose #7452
Babel loose #7452
Conversation
It'd be helpful to document in the performance section that if you're using Babble with the ES6 build then you should use |
that's too bad. are you sure it's the use of Set rather than your spreading of it into an array? IE11 has Set support. you'd just need to forEach over it. have you guys considered composition in lieu of classes (even without function extend(parent, child, props) {
child.__proto__ = parent;
var proto = child.prototype = Object.create(parent.prototype);
proto.constructor = child;
for (var p in props)
proto[p] = props[p];
return child;
} in uPlot i just stick to functions (most of them in a large instance closure) and have no issues with using Buble and the bundles are extremely compact. you have to avoid |
@leeoniya its the spread, but doing forEach with it removes the small speed gain it provides compared to simple object. We've just about finished to conversion to classes, I doubt there are many volunteers to reverse that now. I testet buble and it created about the same code compared to babel loose, only 5kb bigger, because it did not alias |
* Use loose mode for babel * Add note about loose mode in performance docs
loose
mode for babelSet
, because its not handled properly in loose modeCloses: #7448
Babel issue