All Versions
79
Latest Version
Avg Release Cycle
89 days
Latest Release
2616 days ago

Changelog History
Page 2

  • v3.6.3 Changes

    • 🛠 Fix regression in when/callbacks introduced in 3.6.1

  • v3.6.2 Changes

  • v3.6.1 Changes

    • Significant improvements to when.try, and when.lift.
    • ➕ Additional improvements to array functions: when.reduce, when.any, and when.some.
    • 👌 Improved handling of early bail-out cases in when.all, when.map, and when.any.

  • v3.6.0 Changes

    • 🐎 Significant performance improvements:
      • 10x or more for when.map, especially for large arrays
      • ~2x for when.reduce and promise.fold
      • ~1.5-2x for generators using when/generator lift, call, and/or apply.
    • Memory use reductions for when.reduce and promise.fold.

  • v3.5.2 Changes

    • Prevent minifiers from clobbering unhandled rejection reporting if they remove console.* calls. Unhandled rejections will be reported even when using Uglify drop_console.
    • ⚡️ when/function.apply now handles passing an Arguments object directly, e.g. fn.apply(f, arguments);. Use with care: v8 will deoptimize any function where you pass arguments to another function.

  • v3.5.1 Changes

    • when.race & Promise.race now reject with a TypeError if you pass something that is not iterable.
    • 👌 Improve scheduler compatibility with MutationObserver shims
    • Simplify checks for vert.x environment

  • v3.5.0 Changes

    • 👌 Improve when.race & Promise.race performance.
    • Internal changes to start paving the way toward 4.0.0.
    • 🗄 Deprecate when.iterate and when.unfold. Use cujoJS/most for streaming asynchronous values.
    • 🔨 Deprecate progress events. See [the docs for more information](docs/api.md#progress-events-are-deprecated) and [tips on refactoring](docs/api.md#refactoring-progress) code that uses promise progress.

  • v3.4.6 Changes

    • 🛠 Fix webpack compatibility by excluding vertx from browser bundles

  • v3.4.5 Changes

    • 🛠 Fixes for edge cases for unhandled rejection reporting

  • v3.4.4 Changes

    • 👀 Workaround for node 0.10.30 setTimeout bug. See this issue