npm / cli / #1796

97%

latest: 97%

push

Support reporting on ERESOLVE errors when current is missing

While it is somewhat helpful to get reports on this, since it indicates
an underlying problem in Arborist, it's also very disruptive and
unhelpful for users.  As of 2.3.0, Arborist gives us the currentEdge if
available, so we _can_ report on that at least.  If there is no node
_or_ edge, then we just don't say what the current state is, which isn't
useful, but at least is less annoying than a 'property of null'
exception.

PR-URL: https://github.com/npm/cli/pull/3015
Credit: @isaacs
Close: #3015
Reviewed-by: @wraithgar

3023 of 3122 branches covered (96.83%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

5175 of 5318 relevant lines covered (97.31%)

22.28 hits per line