Allow programmatical use of jsinspect about jsinspect HOT 3 CLOSED

Thanks for the issue! I could def expose lib/inspector.js, though it's probably not as helpful without a reporter. In the meantime, it could be accessed with require('jsinspect/lib/inspector') The same goes with the reporters themselves. Someone made a grunt plugin for a similar project, buddy.js, which follows that rough idea https://github.com/eugene-bulkin/grunt-buddyjs/blob/master/tasks/buddyjs.js

As for making it async, it's a CLI tool, and one with the equivalent of tight loops. Introducing async iteration would have a huge impact on performance. And it couldn't really be made async, since there's critical operations that are fully blocking, such as acorn's AST parsing, and the diff generation. I used promises a bit with buddy.js too, and I'll likely switch away from it, as it offers no benefit. Since it's a command line task, and not a server, I don't need to yield execution to any other resources running in that instance of node.

In regards to the results, they can be collected pretty easily by registering a listener to the "match" event. By rendering them progressively, a task would look far more responsive for a large project, rather than batching them all at the end.

I realize this is all just one point of view, but hopefully my reasoning isn't too poor!

from jsinspect.

Hope you don't mind if I close this, and let me know if you have any other comments or suggestions! :)

from jsinspect.

Thanks for your clarifying answer, I don't have anything to ask about this with these explications. 👍

++

from jsinspect.