Back to Explore

kevinbeaty/any-promise

GitHub
2 watchersOpen source

Last release:

Any Promise lets a library work with any ES2015-compatible Promise implementation chosen by the application author. An application can optionally register its preferred Promise (including a global or browser Promise), and libraries can require `any-promise` to get that selected implementation. It can also help older Node.js versions where the global Promise may be unreliable.

Project status

  • The GitHub source (kevinbeaty/any-promise) appears quiet and effectively dormant, with the last upstream push on 2018-10-01 and the most recent tagged updates dating back to 2016, which is long before 2026-06-09.
  • The update cadence is historical and irregular in recent years, with no evidence of ongoing updates since the 2016 series, indicating no active maintenance cycle.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • 1.3.0

    Release 1.3.0 contains no publisher release notes. The code changes mainly add TypeScript declaration files, introduce new “registration shortcut” entry points for many Promise implementations, and update the Promise auto-detection list and browser error messaging. It also updates the project’s test runner and dev tooling, which should not affect runtime consumers directly.

    BreakingFeatures

  • 1.2.0

    Version 1.2.0 introduces a refactor of the registration mechanism by adding a new shared loader module (loader.js) and wiring both Node (register.js) and browser (register-shim.js) through it. Browser behavior changes notably around how window.Promise is validated and how registration can be made local vs globally cached.

    Features

  • 1.1.0

    Release 1.1.0 was published on 2016-02-03, but no release notes were provided by the publisher. As a result, there is no documented information here about new features, bug fixes, breaking changes, security updates, or migration steps.

  • 1.0.0

    This release primarily updates how any-promise selects which Promise implementation to use, and it also refreshes some documentation and CI configuration. The biggest functional change is that the library no longer honors the PROMISE_IMPL environment variable, altering the implementation resolution priority compared to earlier versions.

    Breaking

  • 0.2.0

    Release 0.2.0 was published on 2016-01-29, but no release notes were provided by the publisher. Because the notes are missing, the expected changes, fixes, and potential breaking impacts are not documented here.