v1.2.1

Bugfixes:

• Fix #168

v1.2.0

Features:

• New method: .value()
• New method: .reason()
• New method: Promise.onUnhandledRejectionHandled()
• Promise.map(), .map(), Promise.filter() and .filter() start calling their callbacks as soon as possible while retaining a correct order. See 8085922f.

Bugfixes:

• Fix #165
• Fix #166

v1.1.1

Bugfixes:

• #138
• #144
• #148
• #151

v1.1.0

Features:

• Implement Promise.prototype.tap()
• Implement Promise.coroutine.addYieldHandler()
• Deprecate Promise.prototype.spawn

Bugfixes:

• Fix already rejected promises being reported as unhandled when handled through collection methods
• Fix browserisfy crashing from checking process.version.indexOf

v1.0.8

Bugfixes:

• Fix active domain being lost across asynchronous boundaries in Node.JS 10.xx

v1.0.7

Bugfixes:

• Fix handled errors being reported

v1.0.6

Bugfixes:

• Fix bug with unhandled rejections not being reported
  when using Promise.try or Promise.method without
  attaching further handlers

v1.0.5

Features:

• Node.js performance: promisified functions try to check amount of passed arguments in most optimal order
• Node.js promisified functions will have same .length as the original function minus one (for the callback parameter)

v1.0.4

Features:

• Possibly unhandled rejection handler will always get a stack trace, even if the rejection or thrown error was not an error
• Unhandled rejections are tracked per promise, not per error. So if you create multiple branches from a single ancestor and that ancestor gets rejected, each branch with no error handler with the end will cause a possibly unhandled rejection handler invocation

Bugfixes:

• Fix unhandled non-writable objects or primitives not reported by possibly unhandled rejection handler

v1.0.3

Bugfixes:

• #93