Back to Explore

kevinbeaty/any-promise

GitHub
1 watchersOpen source

Last release: 5/8/2016

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

  • Maintenance status: The source appears to be largely inactive, with the latest documented updates shown in 2016 (v1.3.0, v1.2.0, v1.1.0), and an upstream push last recorded at 2018-10-01, while the project’s description advises “You probably want native promises now.”
  • Update cadence: The last few updates are clustered in early 2016 (Feb 3, then May 3 and May 8), with no further update summaries provided after 2016, suggesting no active release cycle in recent years.

AI summary generated Today

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

Recent updates

  • 1.3.0

    5/8/2016

    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

    5/3/2016

    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

    2/3/2016

    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

    1/31/2016

    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

    1/29/2016

    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.