Skip to content
New issue

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

consider switching to run-auto? #21

Closed
koulmomo opened this issue Jun 30, 2015 · 1 comment · Fixed by #22
Closed

consider switching to run-auto? #21

koulmomo opened this issue Jun 30, 2015 · 1 comment · Fixed by #22

Comments

@koulmomo
Copy link
Contributor

@akshayp @ZeikJT @roderickhsiao

This library only ever uses async.auto yet pulls in all of the async library (thus bloating webpack and browserify) builds.

Thoughts on moving to just using the run-auto lib (used by 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

We could also always wait until async offers modularized exports.

@akshayp
Copy link
Contributor

akshayp commented Jun 30, 2015

sounds good to me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants