[ef4]

I'm going to offer some unsolicited advice. The constructive way to deal with a project that you find interesting but undocumented or otherwise unpolished is to attack. Attack the bugs one by one as you hit them. Go straight to the source and read, read, read.

Ain't nobody got time for that?

Ah, but grasshopper, it seems hugely difficult to you because you lack practice. If you get in the habit of attacking code like this, you will get faster and faster at it. And then the next time a project comes along that's cool, bleeding-edge, and undocumented, you'll just pick it up and be working in no time.

Reading is the secret weapon that turns a mediocre programmer into a great programmer. You need to read a lot of other people's source code. And a situation like the one in this post is ideal: you have a specific problem you're trying to solve, and you have access to all the relevant source code.

If you really don't have time because you need to ship yesterday, then why are you trying to use pre-1.0 software? Go use something boring and proven.

[polshaw]

Why not put that effort into learning JS instead of fixing someone else's JS framework?

[ef4]

Your question implies that frameworks are only for people who don't know Javascript. You might want to reconsider that.