State of bash-parser

@parro-it just wanted to get exactly where this project is at.

While I know there are more bash features that need to be implemented, is it stable in its current state so that it could be built off?

// @milesj

Hi @dthree, nice to see you on the road again :smile_cat:

Well, the AST structure should be stable for both the POSIX and the bash grammars.

The API will be changed soon to solve #43. The change will not be an easy one, but the change in public API signature will be small: parse will return a promise of the AST, and in the option argument, resolvePath callback would have to return a promise, while execCommand and execShellScript.

According to me, we can try the thing in a cash branch. I saw you are going to create a branch for v2 of cash: we can even use that...

There is a dependent package built by @substack on npm from some time now: https://www.npmjs.com/package/falafel-bash, but it's based on an older version of bash-parser. I made a PR there to update the bash-parser version, but it's still unmerged by now...

Great!

API change doesn't seem to be too big a deal.

His package is pretty basic, so not sure that we should worry too much about getting it merged.

I'm actually looking at this for Vorpal 2.0!