From 698cdb0e3117e2a711cf1c897bc1978fe7c91c5f Mon Sep 17 00:00:00 2001
From: Vladimir Starkov <iamstarkov@users.noreply.github.com>
Date: Sun, 23 Oct 2016 13:42:58 +0200
Subject: [PATCH] log plugins' errors in Electron console (#923)

Default `err.message` notification is not helpful,
because it lacks stack and context.

it doesnt hurt for end users to add `console.error(err)`,
because they arent gonna see it. Though, as far as `console.error`
is being logged in Electron console, developers will get
enough information to identify problems with plugin they are developing.
---
 app/plugins.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/app/plugins.js b/app/plugins.js
index 8ed3de3f..a1b00d5e 100644
--- a/app/plugins.js
+++ b/app/plugins.js
@@ -295,6 +295,7 @@ function requirePlugins() {
 
       return mod;
     } catch (err) {
+      console.error(err);
       notify('Plugin error!', `Plugin "${basename(path)}" failed to load (${err.message})`);
     }
   };