I just include this is my package.json at the moment.
"coffee-script": "xixixao/coffee-script"
Have been for the last few months. It uses --> and ==> for generators with version 1.7.1
The only issue I've found with this fork is "if not yield something()" results in a syntax error, but "if not ( yield something() )" works as expected.
Just fork it to your own repo and forget about it until it's added in stable.
You're going to wait a long time for that. I would personally look for an alternative as I feel the project is not being managed properly. Where is CS road map ? there is none. I hope people will definetly move to CS redux ,which seems to be to CS what lodash is to underscore. Same for Backbone,what's the roadmap ? and noone sees a pattern here ?
Somewhat to the side of your main point, but curious what you would be looking for Backbone to add that it needs a roadmap for. I'm not so sure that everything needs a roadmap and to be developing new features. Backbone is IMHO a great example of something that already accomplishes exactly the job it is meant to do, and if you want to do anything else that is your business.
I think Ampersand is the analogue for Backbone. It does the same stuff, but it fully embraces modules, npm, and browserify and it's got great computed properties. These days I work mostly with React, but if Ampersand had existed a year and a half ago I'd have been all over it.
This is incredibly frustrating. It has been sitting around unmerged for nearly a year because they can't decide what the syntax should be. Someone ought to just fork it.
