I can offer a contrary datapoint: As someone who has never used this language before, so has never seen its error messages either before nor after, it took me far longer to parse and understand the "after" error message than the "before"; I immediately saw is not compatible and understood, while the more verbose message doesn't have anywhere near the same clarity --- "But somewhere wanted" made me do a reparse, and I'm still not completely sure what it's trying to say, or what "somewhere" is. Even the "before" is unnecessarily verbose to me --- I'd prefer something more like this:

    Error:%s:%d:%d-%d: incompatible type: expected %s, found %s

Display the error-ing line(s), right inside the terminal.

Seeing that you'd usually focus on a single error rather than trying to get an overview of all errors

IMHO these are not good changes --- chances are that many errors have a common cause which may be far away, and fixing that will make them all disappear. This encourages "code tunnel-vision", making small patches to "fix" each error ("the compiler says the error is here, so I must try to fix it here somehow"), which in the long term can cause massive duplication and decrease the overall quality.

Then again, I don't use JS so maybe the culture is very different, but the "gradual increase of verboseness" seems to be a common trend among other languages, that I strongly disagree with. Writing in six words ("We've found a bug for you!") what could be expressed in one ("Error") does not help anyone except possibly the most noobish of programmers, which one should hope to learn and thereby advance from their level anyway; unless you treat your developers as incapable of learning and disposable, it is counterproductive --- or perhaps I should say un-Reason-able(!) --- to optimise for the extreme beginner at the expense of the experienced.

/rant