In underscore.js you can use like, _.extend(firstObj, secondObj); In jQuery, you can use, $.extend({},firstObj,secondObj); In pure javascipt, you can merge n number of objects by using this function: function mergeObjects() { var resObj = {}; for(var i=0; i < arguments.length; i += 1) { var obj = arguments[i], keys = Object.keys(obj); for(var j=0; j < … Read more
So, what on God’s own green earth is harmony? After ES4 was abandoned, plans were scaled back in a new project which had the code name Harmony. This eventually evolved into ES6. And then what are harmony exports? The exports system that ES6 describes the final (?) version of.
As mentioned in the issue you filed, the core issue is that await* is no longer a thing and has been removed. Unfortunately, it was not properly throwing a syntax error in Babel 6 and was essentially being treated like a normal await. You’ll need to explicitly let [p1, p2] = await Promise.all([ System.import(‘./package1.js’), System.import(‘./package2.js’)]);
Believe it or not… Testing for presence of “=>” in string representation of a function is likely the most reliable way (but not 100%). Obviously we can’t test against either of 2 conditions you mentioned — lack of prototype property and lack of [[Construct]] as that might give false positives with either host objects or … Read more
If your intention is to some other scope, iterate over it, do some other stuff, then be able to iterate over it again later on in that same scope. Then the only thing you shouldn’t try doing is passing the iterator, instead pass the generator: var generator = function*() { yield 1; yield 2; yield … Read more
(shameless but relevant plug below) Caja is reworking its ES5 support via ES5/3 and will do the same for ES harmony. So our structure would be implemented as a Harmony to ES3 layer which can be skipped for real harmony implementations, and then a separable loader that preserves the security properties that concern caja. Like … Read more
Ok, I’ve raised the issue on esdiscuss now and I got an answer from Mozilla’s Jason Orendorff: This is a problem with ES6 maps. The solution will come in the form of ES7 value objects for keys instead of objects. It was considered before to let people specify .equals and .hashCode but it was rejected … Read more
Yes, unfortunately. Except in modules, where it is implied.
From the Arrow functions examples, (() => “foobar”)() // returns “foobar” So, the function invocation operator should be outside. (() => { //… })(); Sample: http://www.es6fiddle.net/hsb8s1sj/
I would say that you should, as a principle, use let whenever it is not inconvenient to do so. Such as: for (let i = 0; i < 100; i++) { // Do something } if (condition) { let msg = a + b + c; console.log(msg); alert(msg); } The advantages to this approach is: … Read more