Transpile dependencies of the test file

[madbence]

ava@0.3 works smoothly on a clean project, but fails to run on mine (tests broke when i've upgraded to from ava@0.2):

(function (exports, require, module, __filename, __dirname) { import {
                                                              ^^^^^^
SyntaxError: Unexpected reserved word

I'm sure it's caused by some weird babel dependency, so it might be unrelated to ava. Last working state is 7d31571, if i try to upgrade to ava@0.3, tests are broken.
I will investigate it tomorrow...

[Qix-]

Did you try rm -rf node_modules and npm i?

What version of Node are you using? Something tells me Babel was removed from compiling tests.

[madbence]

yup, still the same, btw it might be the same as #108 ?

[Qix-]

Yep, that's my guess.

[madbence]

So right now there is no way to test modules directly? I mean, i have to transpile them first, and test the transpiled files?

[sindresorhus]

Implicitly transpiling dependencies in 0.2.0 was a bug that was later fixed 0.3.0. Transpiling dependencies by default is both surprising and slow. I'm open to considering an option for enabling this, but it will not be by default.

[madbence]

what about allowing something like $ babel-node node_modules/.bin/ava ? i'm not really familiar with ava internals, so that's just an idea.

[sindresorhus]

That won't work as we spawn the test files. Just use AVA 0.2.0 until we've figured out how to deal with this. Alternatively use a fork where you've removed this line.

[axross]

I'm open to considering an option for enabling this, but it will not be by default.

I agree. I want to run both tests and target codes for tests with Babel. I think that is proper and as it should be.

[sindresorhus]

What should the option be named?

[sindresorhus]

@floatdrop Any thoughts as to how we should solve this now that #103 has landed?

[floatdrop]

@madbence you can require file with following code in tests as workaround:

// app.es5.js
require('babel/register');
require('./app');

@sindresorhus besides this workaround, not really.

[sindresorhus]

We could set the execPath, when we fork a test file, to the babel-node executable instead of vanilla node.