IMA-WorldHealth / Tree / 19 / 1

70%

master: 70%

push

travis-ci

<a href="https://github.com/IMA-WorldHealth/Tree/commit/eb1df041b">Merge #5

5: Update eslint to the latest version 🚀 r=jniles a=greenkeeper[bot]


## Version **5.0.0** of **[eslint](https://github.com/eslint/eslint)** was just published.

&lt;table&gt;
  &lt;tr&gt;
    &lt;th align=left&gt;
      Dependency
    &lt;/th&gt;
    &lt;td&gt;
      &lt;code&gt;[eslint](https://github.com/eslint/eslint)&lt;/code&gt;
    &lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
      &lt;th align=left&gt;
       Current Version
      &lt;/th&gt;
      &lt;td&gt;
        4.19.1
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;tr&gt;
    &lt;th align=left&gt;
      Type
    &lt;/th&gt;
    &lt;td&gt;
      devDependency
    &lt;/td&gt;
  &lt;/tr&gt;
&lt;/table&gt;



The version **5.0.0** is **not covered** by your **current version range**.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of eslint.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


---


&lt;details&gt;
&lt;summary&gt;Release Notes&lt;/summary&gt;
&lt;strong&gt;v5.0.0&lt;/strong&gt;

&lt;p&gt;&lt;a href=&quot;https://eslint.org/blog/2018/06/eslint-v5.0.0-released&quot; rel=&quot;nofollow&quot;&gt;Release blogpost&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://eslint.org/docs/user-guide/migrating-to-5.0.0&quot; rel=&quot;nofollow&quot;&gt;Migration guide&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class=&quot;commit-link&quot; href... (continued)

17 of 27 branches covered (62.96%)

Branch coverage included in aggregate %.

39 of 64 relevant lines covered (60.94%)

38.81 hits per line