don't depend on esprima#harmony

[jonathanong]

npm is stupid with git dependencies and downloads a copy for every module that depends on them. now my node_modules is 200mb because i have 20 copies of esprima#harmony. any chance to change the esprima dep to a semver range and expect users to install esprima#harmony themselves if they wish?

[redonkulus]

+1 we are having issues as well due to the git+https change. Could you use esprima-fb package to pull in this dependency?

[caridy]

@benjamn since we are not getting any traction on esprima#harmony, should be go with esprima-fb? we should align all the tools, transpilers, etc, to use esprima-fb as well to avoid the npm issues with branches. /cc @eventualbuddha

[benjamn]

I'm not opposed to that, especially since you can always override the version of esprima used.

[eventualbuddha]

Seems good to me. I'm ready to make the switch once recast supports it.

[caridy]

@benjamn good, we are wondering what's going on with the versions you guys are using for that pkg, and figure it you guys can follow semver some how to allow deduping in npm. /cc @jeffmo

[caridy]

ok, confirmed that esprima-fb is following semver, we are good to go!

@benjamn the ball is in your court now ;)

[benjamn]

@zpao @jeffmo can you npm publish the latest version of esprima-fb?

[jeffmo]

5001.1.0-dev-harmony-fb published

[benjamn]

Published v0.7.0 to NPM: https://www.npmjs.org/package/recast

Also did a GitHub release, for the first time ever (better now than never?): https://github.com/benjamn/recast/releases/tag/v0.7.0