We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@akshayp @ZeikJT @roderickhsiao
This library only ever uses async.auto yet pulls in all of the async library (thus bloating webpack and browserify) builds.
async.auto
async
webpack
browserify
Thoughts on moving to just using the run-auto lib (used by webtorrent)?
run-auto
webtorrent
I know that if we do this it will probably mean that a lot of other code/libs needs to switch to using run-auto, run-parallel, and run-series
run-parallel
run-series
We could also always wait until async offers modularized exports.
modularized
The text was updated successfully, but these errors were encountered:
sounds good to me 👍
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
@akshayp @ZeikJT @roderickhsiao
This library only ever uses
async.auto
yet pulls in all of theasync
library (thus bloatingwebpack
andbrowserify
) builds.Thoughts on moving to just using the
run-auto
lib (used bywebtorrent
)?I know that if we do this it will probably mean that a lot of other code/libs needs to switch to using
run-auto
,run-parallel
, andrun-series
We could also always wait until
async
offersmodularized
exports.The text was updated successfully, but these errors were encountered: