Henry

If you are cool with doing releases on v6 I definitely wouldn't be opposed?

I don't think we ever intended Babel standalone to be used in "prod" but interesting to hear that. It's also not actively maintained if that wasn't clear since we have...

@benjamn So we could switch out `babel-generator` for `recast.print` to keep original formatting (assuming you wanted something like jscodeshift/eslint autofix/run babel like `babel src --out-dir src`?

A babel transform/babel = `babylon + babel-traverse + babel-generator` so you could modify the ast with a babel transform and output to something that can consume a babel AST (recast)?

Ok I'm just wondering what we can do to make recast + babel interop better if that's possible. I think it would be nice to be able to write a...

@benjamn would recast have to parse it like `recast.parse(source, { parser: require("babylon") });` or can you still use babylon on its own? Just wanted to know what changes would need...

Ok I can test it my modifying babel's transformation step to take in a different parser/generator. I think the last thing is to accept babel AST nodes in ast-types? Since...

@benjamn yay something like this seems to work https://github.com/babel/babel/pull/3561 or it would be cool if we could subsitute with babel-types @mohebifar @nene I can help with converting when it's possible....

As a update for this to happen: - [x] https://github.com/babel/babel/pull/3561 in babel-core needs to land in some form (probably a option to pass a string (similar to a plugin) that...

https://github.com/babel/babel/pull/3561 has landed! So writing a plugin that doesn't include the different AST nodes should work now https://github.com/babel/babylon#output