User blog comment:Rappy 4187/Technical Update: August 31, 2015/@comment-24473195-20150831233511/@comment-126761-20150901121629

Reducing the potential for JS errors is something we've spent some time thinking about - we're looking at a few different approaches, which you'll like see some effects of over the next few months. Certainly, we don't want such errors to go unnoticed and thus linger.

Edit: I've just been reminded, we did actually do a sweep a while back to check for JS errors on our busier communities, and fixed what we could. We don't think doing that repeatedly is a good long-term solution, of course.