[Snyk] Security upgrade async from 2.1.4 to 3.0.0

[lmaeda]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Arbitrary Code Injection SNYK-JS-LODASH-15869625	183
	Prototype Pollution SNYK-JS-LODASH-15869619	88

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection

[lmaeda]

This major version upgrade from async v2 to v3 introduces significant breaking changes, primarily in the async.queue API.

Key Breaking Changes:

• queue.drain API Change: The way to set a callback for when a queue has finished processing all items has changed. In v2, drain was a property to be assigned. In v3, it is a function that accepts the callback. This change will break existing queue implementations.

  • v2 syntax: q.drain = function() { ... };
  • v3 syntax: q.drain(() => { ... });

• Native async/await Support: The library now has first-class support for native ES2017 async functions. While this is a feature, developers using transpilers like Babel must wrap their async functions in async.asyncify() for them to work correctly.

Recommendation:
Code using async.queue must be updated to use the new drain() function syntax. Review all queue implementations to prevent runtime errors.

Source: Package documentation and GitHub issue discussions.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.