Extending Promises in ES6

Question

I am trying to extend Promise:

class PersistedPromise extends Promise { }

Then call the static resolve on the derived class to directly create a resolved promise:

PersistedPromise.resolve(1)

In traceur, this yields:

ModuleEvaluationError: #<PersistedPromise> is not a promise
    at new PersistedPromise (~rtm/gen/promise.js:6:57)
    at Function.resolve (native)

In Babel (run as babel-node --experimental promise.js) it results in:

    Promise.apply(this, arguments);
            ^
TypeError: [object Object] is not a promise
    at new PersistedPromise (~rtm/gen/promise.js:1:23)
    at Function.resolve (native)
    ...

I was depending on this:

All static methods of Promise support subclassing: they create new instances via their receiver (think: new this(...)) and also access other static methods via it (this.resolve(...) versus Promise.resolve(...)).

from http://www.2ality.com/2014/10/es6-promises-api.html.

It appears that node checks the this on calls such as Promise.resolve.call(this, val) for being a Promise, rather than (correctly?) Promise or a derived class thereof (v0.12.0).

Is the above no longer operative, or did not make into the spec, or just not implemented by traceur and/or node?

That should work imo. My guess is that neither of the transpilers supports this. — Bergi, Mar 29 '15 at 22:13
**New Viewers Note** - the code example in this question should now compile and work in Babel. — Benjamin Gruenbaum, Apr 18 '15 at 07:55
@BenjaminGruenbaum I am using Babel + ES2015 preset and I am still getting `TypeError: # is not a promise` when I call the constructor `new ExtendedPromise(res => {})`. Is there any other trick to this? — sighrobot, Mar 01 '16 at 21:38
@sighrobot probably because you're not using the polyfill and/or are on a browser which offers native promises. — Benjamin Gruenbaum, Mar 01 '16 at 21:44
@BenjaminGruenbaum The polyfill is needed even if the browser natively supports promises? — levi, Mar 10 '16 at 22:23

score 20 · Accepted Answer · edited Dec 15 '16 at 03:10

Is the above no longer operative, or did not make into the spec, or just not implemented by traceur and/or node?

ES6 promises in the spec support subclassing. That is, you will eventually be able to subclass promises the way you just did. This is by design.

That said, none of the browsers currently follow that spec correctly in this regard - as far as I know only the ES6-promise shim, Babel (core-js) and RSVP follow ES6 semantics with regards to subclassing correctly. Support in browsers is eventually coming but it's not there yet. Hold tight.

Here is a list of currently supporting implementations.

Extending Promises in ES6

1 Answers1

Linked