Closed fixplz closed 8 years ago
+1
Agree about the status of babel 6, hopefully things will progress quickly but it's very dependent on one author at the moment and really needs more people involved.
I'm still considering what to do here because I can't use babel6 in my projects yet either, but a lot of work has gone into v3 of the plugin and the prospect of backporting things seems... daunting. It's certainly possible but I don't know whether I have the enthusiasm to do it right now as my free time is limited at the moment. A spirited fellow committer (hint hint) might be able to do it as I don't think we actually rely on any new babel6 functionality, but a lot of node types have changed, been split up etc so it's not just a case of find/replace.
I will publish the latest v2 a bit later this evening.
Closing this, for me I think focussing on babel6 is more important. Feel free to reopen if you don't mind doing this yourself
Please publish at least commit 10e6a04 to NPM, maybe together with some other applicable fixes from v3.
I haven't been able to test v3 much because Babel v6 is a mess and doesn't work for any of my projects. (It's currently quite user-hostile so I'm not sure how they're treating it as stable.)