Improve/change logging

[unional]

Could it because the error logging: typings ERR! message ... and so on are too "formal" and similar to npm error message so that when people see the error, they freak out and think there must be some fatal errors.

Therefore they file issue with the message attached instead of just reading the message and figure out why?

For sure we see this behavior a lot.
Maybe soften up the messages would help?

[unional]

Cross reference
typings/typings#573

[blakeembrey]

I would like that, but I couldn't think of how to make it easier. We could stop adding "caused by", but that's been very helpful for knowing the underlying issue. I can't think of any way to improve scenario one unless we fallback to searching for the entry? E.g. try to install, fallback to search by name, prompt move likely action.

For scenario two, it's easy enough to add "Did you mean to add the --global flag?".

[unional]

Last option is good.

I think it's just the presentation need to change. Not the content. :)