Please disable interactive 'anonymously report usage' message during install

[doliver3]

Hi,

First, I just found this Typings project and really believe what you are doing is so necessary to allow distributed control of typing without the need to wait for the authors to publish new versions. Anything that can be done to ensure types match versions and to ensure types can be patched quickly is wonderful. Thanks for putting this together, and I hope many use it!

I'm opening this issue because the npm install stopped in the middle of the install with this message and it hung there until I responded.

May typings anonymously report usage statistics to improve the tool over time? No

Could you provide a way to ensure that this message does not occur and block activity during the install process?

I have an installation script that pulls the dependencies and I don't want to require that script to be interactive.

Bower tried to do the same thing not long ago, and it was hugely unpopular because it stopped the installation process in the middle.

bower/bower#1102
http://stackoverflow.com/questions/22387857/stop-bower-from-asking-for-statistics-when-installing

I really don't want to echo a Y to the npm install -what if some other package decides to go interactive? Then the Y was to the wrong prompt.

Perhaps if we must keep a prompt in place, could you provide some npm flag or environment variable or something that could be set that would avoid prompting and halting the install?

Thanks,
David

[blakeembrey]

Can you please give me more information on your installation script? I'm interested because I've been using this with CI since release and haven't run into any issues, which is odd that you're now hitting them. While I'm all for making it easier to use and I don't have an issue disabling this, it's likely analytics will come in handy in the future (right now it's useful to see whether there's any traction or whether people are getting stuck).

Also, the insights are automatically disabled with process.env.CI, process.stdout.isTTY or using the --no-insight flag (see https://github.com/yeoman/insight/blob/master/lib/index.js#L106).