JFG Media

The plugin catches most JS errors, logs them, and displays them in a dashboard widget.
Here are some of its features:
<ul>
<li>
Except for the plugin settings, there is no database storage involved. Log is written in a “.log” file.
</li>
<li>
Display latest JS errors in a dashboard widget.
</li>
<li>
Refresh errors from the dashboard widget.
</li>
<li>
See the full error log on a separate page.
</li>
<li>
Ignore errors if the user agent contains a specific string.
</li>
<li>
Ignore errors if the error contains a specific string.
</li>
<li>
Ignore errors if the script url contains a specific string.
</li>
<li>
See which page and which script triggered the errors.
</li>
<li>
Choose the maximum amount of errors to log per page load.
</li>
<li>
Exclude logging errors from specific post types.
</li>
<li>
Choose how ajax calls are made.
</li>
</ul>
<h4>Developer hooks and filters</h4>
The plugin cleans the log every 24 hours, to only keep the last 100 entries. 
You may use the “jserrlog_max_log_entries” WP filter to enable more or less entries, by returning an integer: <code>add_filter('jserrlog_max_log_entries',function(){return 200;})</code>
Alter error data: 
You may use the “jserrlog_pre_insert_error” WP filter to modify the error data before it’s inserted into the log file: <code>add_filter('jserrlog_pre_insert_error',function($error_data){return $error_data;})</code>
Trigger integrations: 
You may use the “jserrlog_after_log” WP hook to trigger an action (Slack notification, etc.) after an error was logged: <code>add_action('jserrlog_after_log',function($error_data){//do something})</code>
Backup old errors: 
You may use the “jserrlog_before_log_maintenance” WP hook to trigger an action (archive errors, etc.) before old errors are deleted: <code>add_action('jserrlog_before_log_maintenance',function($errors){//do something})</code>
<h4>Multisite</h4>
The plugin works with multisite. There’s one error log per site.

JS Error Logger

Logs front-end javascript errors, and displays them in a dashboard widget

10up

Zack Tollman

At the first sign of trouble, an ostrich buries its head in the sand. Ostrichcize allows a plugin or theme developer to 
bury his or her head in the sand by turning off error reporting for select plugins or the current theme.
If you have ever installed a plugin or worked on a site with a plugin that throws numerous of errors and notices, but do 
not have the time to fix the issue, you can turn off those notices with this plugin. By simply filtering the plugin, you 
can add to the list of plugins for which no notices will be shown.
To add to this list simply write something like:
<pre><code>function my_ostrichcized_plugins( $slugs ) {
 $slugs[] = 'debug-bar-cron';
 return $slugs;
}

function my_pre_my_ostrichcized_plugins() {
 add_filter( 'ostrichcized_plugins', 'my_ostrichcized_plugins' );
}

add_action( 'plugins_loaded', 'my_pre_my_ostrichcized_plugins', 1 );
</pre>
</code></pre>
Note that the filter must be added before any offending code is run in order to redefine the error reporting function 
before it is first called. The means that in most cases, this code will need to run from a plugin and not a theme.
To turn off PHP error reporting for a theme, run:
<pre><code>function my_ostrichcize_theme() {
 add_filter( 'ostrichcize_theme', '__return_true' );
}
add_action( 'plugins_loaded', 'my_ostrichcize_theme', 1 );
</pre>
</code></pre>
Thanks to Jeremy Felt (@jeremyfelt) for assistance naming the plugin!

Ostrichcize

Hide PHP error reporting for specified plugins or the current theme.

JS Error Logger vs Ostrichcize