Mark Wubben

Looks like the explicit `process.execArgv` reference was added for a debugging feature back in 2016: https://github.com/avajs/ava/pull/874 The problem though is we need to pass a flag to enable source maps,...

Having thought about this some more, we _could_ add a `filterExecArgv()` through the `ava.config.*` files. It could receive the individual values allowing end-users to discard incompatible ones. As for documentation,...

See also https://github.com/avajs/ava/issues/3025.

I think a filter function could be a useful addition, so I'll leave this open for now.

Do you have a stack trace for that error? The pattern is resolved against to the current working directory and then made relative against the project directory: https://github.com/avajs/ava/blob/63987725957114ea92dab430b7795ecc649ff107/lib/cli.js#L419 However it...

Alternatively the line above: https://github.com/avajs/ava/blob/678f9caf22343ba05efd54cbfebb37962f590cab/lib/serialize-error.js#L109 [That function is pretty old](https://www.npmjs.com/package/clean-yaml-object), there must be a better alternative nowadays. If the cause has a cause, how do you suggest we format that?

I like it! @bitjson are you game to implement this? Let me know if you need some pointers.

Hi @bitjson, I think the `meta` object is defined here: https://github.com/avajs/ava/blob/c74934853db1d387c46ed1f953970c777feed6a0/lib/runner.js#L71-L77 It's then made available through the CJS and ESM entrypoints and some indirection. `Runner` is instantiated here: https://github.com/avajs/ava/blob/c74934853db1d387c46ed1f953970c777feed6a0/lib/worker/base.js#L78 The...

> Bumping @babel/register to ^0.5.0 would fix the problem with Babel and AVA? Yes, until there's a `0.6.0`. At least with a 1.0 release you can ship new features without...

> Still, I think 1.x is a good idea. Yay! > It could be nice to wait for source-map to release an 1.0 though, and then we could upgrade to...