async
3.2.6 · 19 Aug 2024MIT149.5M / weekRepositoryHomepagenpmAtom feed
Upgrading async From 1.5.2 to 2.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 11
- changes to make
- 0
- advisories fixed
- 18
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
Security
1 advisory still affects 2.0.0
- Prototype Pollution in asynchigh · GHSA-fwr7-v2mv-hh25
Upgrading to 2.6.4 clears it.
Release by release
- Breaking
- Breaking
- Breaking
- Breaking
6 other lines we could not sort, mostly version bumps
- 2.0.0
Takes a variable number of arguments
- 2.0.0
The last argument is always a callback
- 2.0.0
The callback can accept any number of arguments
- 2.0.0
The first argument passed to the callback will be treated as an error result, if the argument is truthy
- 2.0.0
Any number of result arguments can be passed after the "error" argument
- 2.0.0
The callback is called once and exactly once, either on the same tick or later tick of the JavaScript event loop.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.