It would certainly be nice just to support the latest version of Jasmine in Chutzpah, but I don't think it's realistic for most folks who've been using that framework. As the OP said, updating to use the new spy, custom matcher and async APIs isn't necessarily hard, but it could be very time consuming for large suites of specs. Only supporting 2.0 would unfortunately be a significant breaking change, break lots of builds and probably get people into trouble.
- Sadly yes.
- Yes, I do think the latest should be the default. There will be some noise, but as long as there is a clear workaround I think most folks would be able to move forward.
-
Unfortunately no.