Allow programmatic usage

[danburzo]

No description provided.

[phenax]

Can I work on this issue?

[danburzo]

Yes, that would be great! Let's outline how we can move some things around in an interface that makes sense. I guess we can start by having a separate cli.js file for the CLI and leave index.js for exporting the bundle and cleanup methods.

In the future, I see more of the steps as being configurable. I'll get back on this thread once the thought crystallizes.

[phenax]

Awesome!
I'll start by moving the commander stuff to a cli.js and get a PR ready.
Btw, I feel like a node api shouldn't log to the console so we should remove the console.log's out of the api by either splitting the function into smaller parts so the cli can add console logs in between and the node api will export a non-console log version of it. Or it can return an instance of an event emitter in which case the node api will emit lifecycle events and the cli will console log on those events.
Either way, it is an enhancement deserving another PR. What do you think?

[danburzo]

Btw, I feel like a node api shouldn't log to the console so we should remove the console.log's out of the api by either splitting the function into smaller parts so the cli can add console logs in between and the node api will export a non-console log version of it.

Agreed. The only really useful output from the program is the path to the temporary HTML. As we figure out how programmatic usage will look like, we may have the opportunity of either having the library expose a log() method or, as you said, an event emitter.