Monitor client errors?

[Fil]

Problem: a developer might not see that a page errors (client-side), and might ship a broken dashboard.

Two ideas for mitigation:

• Notify the preview server of client-side errors; this would keep a running list of pages that have had errors. One step of the build would then list the erroring pages (that we know about), optionally halting build.
• Monitor same in the hosted version, optionally sending an urgent message to the developer. Before we notify, we have to be careful about legitimate, transient errors (maybe some resource didn't load, or the client is using MSIE). But if as a developer you have to maintain 100 pages and you see (in a meta-dashboard) that 1 of them regularly errors, it can be a tremendous help.

[Fil]

@chriscooning this issue is about "CI" (one of the tests we can do before deploying). There could be more.