shinnn / is-resolvable / 14 / 1

100%

master: 100%

push

travis-ci

<a href="https://github.com/shinnn/is-resolvable/commit/<a class=hub.com/shinnn/is-resolvable/commit/bb3dbe737462401e78213c1b7f73e7ccaf3064dc">bb3dbe737<a href="https://github.com/shinnn/is-resolvable/commit/bb3dbe737462401e78213c1b7f73e7ccaf3064dc">&quot;&gt;use native try-catch since it&amp;#39;s well optimized today

https://github.com/davidmarkclements/v8-perf/tree/</a><a class="double-link" href="https://github.com/shinnn/is-resolvable/commit/<a class="double-link" href="https://github.com/shinnn/is-resolvable/commit/75d3e240fca01a1286f7d69f66102f7c868a2d58">75d3e240f</a>">75d3e240f</a><a href="https://github.com/shinnn/is-resolvable/commit/bb3dbe737462401e78213c1b7f73e7ccaf3064dc">#the-trycatch-problem

&gt; We can see that the existing wisdom around `try/catch` causing performance problems is true in Node 6 (V8 5.1) but has significantly less performance impact in Node 8.0-8.2 (V8 5.8).
&gt;
&gt; Also of note, calling a function from within a `try` block is much slower than calling it from outside a `try` block - this holds true in both Node 6 (V8 5.1) and Node 8.0-8.2 (V8 5.8).
&gt;
&gt; However for Node 8.3+ the performance hit of calling a function inside a `try` block is negligible.

2 of 2 branches covered (100.0%)

26 of 26 relevant lines covered (100.0%)

2.31 hits per line