<p dir="auto">One project I'm working on has three different places where I need to pass options to 6to5. There's the test suite that runs ES6 code with <code class="notranslate">6to5/register</code>, the Gulpfile that builds ES5 code that I can <code class="notranslate">npm publish</code>, and the REPL.</p>
<p dir="auto">Keeping all three in sync is not easy, especially when configurations change (e.g. just released 3.0). What about having all three reading their configuration from the same file?</p>
<blockquote>
<p dir="auto">Issue originally made by Jon Moss (maclover7)</p>
</blockquote>
<h3 dir="auto">Description</h3>
<p dir="auto">It seems like we are double testing Babel on both CircleCI and TravisCI. The only purpose of Circle appears to be to run tests on Node.js version [[ https://github.com/babel/babel/blob/master/circle.yml#L4 | 0.10.0 ]], which is already [[ https://github.com/babel/babel/blob/master/.travis.yml#L14 | duplicated ]] in the Travis build configuration. I propose that we remove the Circle integration, as this wastes resources, and also also slows down PR build times.</p>
<p dir="auto">Happy to send in a PR to take care of this, although may require a repo admin to go to Circle's site and manually turn off the integration. :-)</p>