Parallelism using workerpool

[simonihmig]

Closes #11

Worth noting:

• this changes to signature of some public (exposed in index.js) function to return a Promise, so again kind of a breaking change. I don't know if this is used anywhere besides my WIP addon though, so not sure if we have to bump the major version. I guess we can ignore this until these exposed functions have become more "official" (addon is published, functions are documented)?
• although the summarize function is not really working asynchronously, I nevertheless changed it also to return a Promise, so we can change the implementation a bit under the hood (like not using the ...Sync() node functions or so, if that makes sense)
• I removed some of the spinner feedback ("processing: <bundleName> ...") from the CLI, as it did not make so much sense when bundles are processed in parallel. (the messages all show up at once, or rather only the last message is visible as the previous are replaced)

[stefanpenner]

@simonihmig sorry for the delay, I was on vacation. I left 1 comment, otherwise this looks good.

Could you also share before/after times for a medium sized app? I would like to be sure we are seeing some improvements.

[simonihmig]

sorry for the delay, I was on vacation

no need for excuses! 😉

Could you also share before/after times for a medium sized app?

I wrote that down, but unfortunately lost that note 🙄. IIRC it was around 2min vs. 50sec, but I will check again when I look at the exit code question (which is a valid concern!).

[stefanpenner]

I wrote that down, but unfortunately lost that note 🙄. IIRC it was around 2min vs. 50sec, but I will check again when I look at the exit code question (which is a valid concern!).

As long as you did test it manually, thats good enough for me. I just wanted to be sure it did actually work (i expected it too).

[stefanpenner]

@simonihmig LGTM, let me know if this is ready, i'll gladly merge + release.

[simonihmig]

@stefanpenner go for it! 🎉

[stefanpenner]

released as v4.2.0 🎉