gustavnikolaj / async-main-wrap / 334 / 2

100%

master: 100%

push

travis-ci-com

<a href="https://github.com/gustavnikolaj/async-main-wrap/commit/<a class=hub.com/gustavnikolaj/async-main-wrap/commit/d8c5b851b83b0432531908c5155b4a8533307993">d8c5b851b<a href="https://github.com/gustavnikolaj/async-main-wrap/commit/d8c5b851b83b0432531908c5155b4a8533307993">&quot;&gt;Update esm: 3.2.0 → 3.2.5 (patch) (#105)

* Update esm to version 3.2.5

* Fix esm integration.

In esm@3.2.0 a regression was introduced that enabled a cjs export mode
by default. Previously the default export would be available under the
default key, but it was now exported like `module.exports = foo` would
be in regular common js.

It was then fixed in version 3.2.2 I believe, but the test here has
remained broken since.

I removed `.default` from the require statement when updating to 3.2.0
in commit &lt;/a&gt;&lt;a class=&quot;double-link&quot; href=&quot;https://github.com/gustavnikolaj/async-main-wrap/commit/&lt;a class=&quot;double-link&quot; href=&quot;https://git">&lt;a class=</a>hub.com/gustavnikolaj/async-main-wrap/commit/<a class=hub.com/gustavnikolaj/async-main-wrap/commit/a20690cbfb8a1e8f4d04ee04b89e7380e86dd386">a20690cbf">a20690cbf</a><a href="https://github.com/gustavnikolaj/async-main-wrap/commit/d8c5b851b83b0432531908c5155b4a8533307993">:

commit a20690cbfb8a1e8f4d04ee04b89e7380e86dd386
Author: depfu[bot] &lt;depfu[bot]@users.noreply.github.com&gt;
Date:   Fri Feb 1 15:54:40 2019 +0100

    Update esm: 3.1.4 → 3.2.0 (minor) (#94)

    * Update esm to version 3.2.0

    * Fix example for esm integration

    After esm@3.2.0 the default export is actually what you get when you
    import the module with cjs require. Previously, it would be on the
    exported object under the default key.</a>

21 of 21 branches covered (100.0%)

Branch coverage included in aggregate %.

28 of 28 relevant lines covered (100.0%)

7.07 hits per line