Go over several techniques for reporting errors that happen in client-side JS code in a fair amount of detail.

JS errors happen in the wild, and these errors never feed back to the developer. Considering that apps are getting more complex JS-wise, it's becoming increasingly important to find out about these errors. This talk will go over some 6-7 different mechanisms for reporting errors back to the developer. It'll end by introducing Errorception (http://errorception.com/) - a service I built, which relies on one of those mechanisms.