App hangs on first run if run non-interactively

[zuzak]

At the moment, if you run the prototype kit for the first time in an non-interactive way (say, as part of a Unix pipeline, or deployed into Kubernetes), the app will hang waiting for user input to opt into sharing usage data.

Perhaps we should default to "no" when this happens? For example:

diff --git a/lib/usage_data.js b/lib/usage_data.js
index 898e765..4083ce0 100755
--- a/lib/usage_data.js
+++ b/lib/usage_data.js
@@ -17,6 +17,7 @@ exports.getUsageDataConfig = function () {
   try {
     usageDataConfig = require(path.join(__dirname, '../usage-data-config.json'))
   } catch (e) {
+    if (!process.stdout.isTTY) return {'collectUsageData': false}
     // do nothing - we will make a config
   }
   return usageDataConfig

[NickColley]

One alternative would be to remove the tracking if we find it has served it's purpose, for example there's nothing more we can learn.

[NickColley]

@zuzak it seems sensible to default this to off if we know for sure the application is run by the user.

I think we would accept a pull request for what you've described here if it were also tested :)

Let me know if you need any help doing that. We can also pick this up when we get some time in the future.