Can we make roco asynchronous and api friendly?

A lot of `existsSync`, `readFileSync`, `readDirSync` calls exists at the moment.
`process.exit` buried deep in code — it should be moved out to `bin/roco` imho.
https://github.com/1602/roco/blob/master/lib/rockout.js#L300

I'm really like how it looks but need async and more configs, e.g. pass writable streams to catch remote output, make a prefix with time, disable (or overwrite) string colorize methods, etc.
Can we do something with it?

The issue points to lib/rockout.js line 300 as an example of a synchronous call and deep process.exit. Start by examining the codebase for all fs.existsSync, readFileSync, readdirSync, and process.exit calls. Understand the flow from bin/roco through the deployment steps. 'Done' means replacing sync calls with async/await or promises, moving exit handling to the CLI entry point, and designing a configurable API for streams, prefixes, and colorization.

Vom Indexierungsmodell aus dem Issue-Text verfasst.