Yes, this is intentional (a part of the spec). If an object has an own property (.property in your example), this property will be used and not an inherited one. If that property is existent, but is an accessor property without a getter, then undefined will be returned. Notice that this behaviour has not changed … Read more
I’ve started employing the import * as obj style within my tests, which imports all exports from a module as properties of an object which can then be mocked. I find this to be a lot cleaner than using something like rewire or proxyquire or any similar technique. I can’t speak for traceur which was … Read more
it’s not being removed from the WeakSet. Why is that? Most likely because the garbage collector has not yet run. However, you say you are using Traceur, so it just might be that they’re not properly supported. I wonder how the console can show the contents of a WeakSet anyway. What is the point of … Read more
No, there are no nested class scopes in ES6, and there is no such thing as private members in the class syntax anyway if you mean that. Of course you can put a second class as a static property on another class, like this: class A { … } A.B = class { … }; … Read more
There are no private, public or protected keywords in current ECMAScript 6 specification. So Traceur does not support private and public. 6to5 (currently it’s called “Babel”) realizes this proposal for experimental purpose (see also this discussion). But it’s just proposal, after all. So for now you can just simulate private properties through WeakMap (see here). … Read more
someClassInstance.constructor.name is exactly the correct way to do this. Transpilers may not support this, but it is the standard way per the specification. (The name property of functions declared via ClassDeclaration productions is set in 14.5.15, step 6.)