PackageTrack Sign in Track my project

inflight

Add callbacks to requests in flight to avoid async duplication

· 355M downloads/mo #736 most downloaded on npm npm/inflight

What this package is like to depend on

Last release 10 years ago

no release in 18 months

Release timing varies

gaps range from 2 weeks to 1.6 years

Unknown

no stable releases

7 versions withdrawn

withdrawn after publishing

12 years old

7 releases · first in 2014

0 releases in the last 12 months

see the full history below

Release timeline

7 releases · May 2014 to Oct 2016
2015 2017 2019 2021 2023 2025
Release Pre-release Withdrawn

Releases

latest 7
  1. 1.0.6 13 Oct 2016 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.5 and v1.0.6 there were 6 commits, 5 of them substantive:

    • cleanup even if a callback throws (fixes #1)
    • add travis config
    • attempt to fix with finally
    • update tap, enforce 100% test coverage, verify thrown error is expected error
    • Add comment that zalgo cb's get re-queued even in the event of a throw
  2. 1.0.5 18 May 2016 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.4 and v1.0.5 there were 4 commits, 3 of them substantive:

    • tap@1.2.0
    • package: fix repository link
    • add files entry to package.json
  3. 1.0.4 03 Oct 2014 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.3 and v1.0.4 there were 2 commits, 1 of them substantive:

    • pass arbitrary numbers of parameters to callers
  4. 1.0.3 01 Oct 2014 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.2 and v1.0.3 there were 2 commits, 1 of them substantive:

    • Prevent a very edgy zalgo-related race condition
  5. 1.0.2 18 Sep 2014 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.1 and v1.0.2 there were 2 commits, 1 of them substantive:

    • use wrappy for property transfer
  6. 1.0.1 05 May 2014 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Commits, not release notes

    This project publishes no release notes. Between v1.0.0 and v1.0.1 there were 4 commits, 3 of them substantive:

    • add description to package.json
    • Fix bug in example code
    • test
  7. 1.0.0 05 May 2014 withdrawn

    This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.

    Nothing published for this version

Stop reading changelogs one package at a time.

Point PackageTrack at your project and get told which of your dependencies moved, which of those matter, and what to do about it.

Track my project