You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the current version of async (3.2.6) from source, I get several warnings about security issues in outdated packages. One potential way of addressing this is to use babel 7.x and @rollup/plugin-node-resolve instead. I have changed what is needed to get it to build on Debian (which no longer has some of the Node.js packages listed in package.json), and the diff is below. I'm not submitting it as a PR yet, as it will certainly also need changes to the package.json file and possibly elsewhere, but I could do so if you wished.
I also (locally) modified the test directory to allow for testing of the dist/async.js module (rather than the lib/* source files), and all the tests passed except for should error when re-assigning event methods in test/queue.js. I don't know if that is as a result of the changes below or an unrelated problem.
I'd be open to the babel update. I'd also want to make sure babel-plugin-add-module-exports does not significantly change the output or add too much extra boilerplate for "correctness" we don't need.
Hi!
When building the current version of async (3.2.6) from source, I get several warnings about security issues in outdated packages. One potential way of addressing this is to use babel 7.x and
@rollup/plugin-node-resolve
instead. I have changed what is needed to get it to build on Debian (which no longer has some of the Node.js packages listed inpackage.json
), and the diff is below. I'm not submitting it as a PR yet, as it will certainly also need changes to thepackage.json
file and possibly elsewhere, but I could do so if you wished.I also (locally) modified the test directory to allow for testing of the
dist/async.js
module (rather than thelib/*
source files), and all the tests passed except forshould error when re-assigning event methods
intest/queue.js
. I don't know if that is as a result of the changes below or an unrelated problem.The text was updated successfully, but these errors were encountered: