<p dir="auto">For example: <a href="https://github.com/6to5/6to5/tree/master/lib/6to5/transformation/transformers/es6-generators">https://github.com/6to5/6to5/tree/master/lib/6to5/transformation/transformers/es6-generators</a></p>
<p dir="auto">You're effectively forking the code, and making it much more difficult for you to incorporate updates quickly (or contribute changes upstream). It's unclear what version of Regenerator these files even represent. I don't understand the benefit you imagine this has for 6to5 or any of its contributing libraries. This isn't how open source should work!</p>
<p dir="auto">Sorry for the alarmist tone, but this is a real problem. I'm happy to work with you to make Regenerator easier to use as an NPM package.</p>
<p dir="auto">Thanks.</p>
<p dir="auto">We currently - now after jest has been landed in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="301067338" data-permission-text="Title is private" data-url="https://github.com/babel/babel/issues/7455" data-hovercard-type="pull_request" data-hovercard-url="/babel/babel/pull/7455/hovercard" href="https://github.com/babel/babel/pull/7455">#7455</a>  - have a mix of different assertion methods in tests.</p>
<ul dir="auto">
<li>There is <code class="notranslate">chai</code> in use.</li>
<li>There is <code class="notranslate">assert</code> in use.</li>
<li>There is jests <code class="notranslate">expect</code> in use.</li>
</ul>
<p dir="auto">The first two should be removed and rewritten to make use of <code class="notranslate">expect</code> which comes with jest.</p>
<p dir="auto">so for example</p>
<div class="highlight highlight-source-diff notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="-import chai from &quot;chai&quot;;
-import assert from &quot;assert&quot;;
-
-chai.expect(actualCode).to.be.equal(&quot;var fn;&quot;);
+expect(actualCode).toBe(&quot;var fn;&quot;)
-assert.strictEqual(this.constructor, Bar);
+expect(this.constructor).toBe(Bar)"><pre class="notranslate"><span class="pl-md"><span class="pl-md">-</span>import chai from "chai";</span>
<span class="pl-md"><span class="pl-md">-</span>import assert from "assert";</span>
<span class="pl-md"><span class="pl-md">-</span></span>
<span class="pl-md"><span class="pl-md">-</span>chai.expect(actualCode).to.be.equal("var fn;");</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>expect(actualCode).toBe("var fn;")</span>
<span class="pl-md"><span class="pl-md">-</span>assert.strictEqual(this.constructor, Bar);</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>expect(this.constructor).toBe(Bar)</span></pre></div>
<p dir="auto">The jest matchers should be used as good as possible, so for example not <code class="notranslate">expect(x &gt;= 3).toBe(true)</code> but instead <code class="notranslate">expect(x).toBeGreaterThanOrEqual(3)</code></p>
<p dir="auto">The doc of jests matchers is here: <a href="https://facebook.github.io/jest/docs/en/expect.html" rel="nofollow">https://facebook.github.io/jest/docs/en/expect.html</a></p>
<p dir="auto">As we have a lot of tests split up in a lot of packages this task can also be split up and only one/some package(s) at a time be migrated.</p>