Add a config file.

[jamestalmage]

Probably just an ava section in package.json.

The available options are getting complex enough that I think we are close to needing this (if we aren't there already).

{
  "serial": true,
  "verbose": true,
  "cache": false
}

These would need to be merged with whatever is specified on the command line (command line taking precedence).

The goal is to be able to specify the default way you want it to behave when you simply type ava on the command line.

[sindresorhus]

👍 I do that with XO too. I would prefer only a section in package.json. Makes things simple.

https://github.com/sindresorhus/pkg-conf

[ariporad]

Agreed. I'd also like to add a "files" section, and have it be "config.ava", vs. "ava "

[sindresorhus]

I'd also like to add a "files" section

👍

and have it be "config.ava", vs. "ava "

👎 That's a convention nobody uses. Top-level is simpler and it will never conflict with anything anyways.

[jamestalmage]

That's a convention nobody uses

Except for istanbuljs/nyc#131 😄

[jamestalmage]

I'd also like to add a "files" section

Yeah, I think basically any config value is fair game. I can't think of one we shouldn't allow them to configure this way.

[vadimdemedes]

Great suggestion, I'm on board!

[ariporad]

@sindresorhus: Except nyc and comitizen (off the top of my head).

[jamestalmage]

nyc is falling off that list very soon: istanbuljs/nyc#132

[kentcdodds]

Add ghooks to the list of modules that use the config convention :-) But meh, it'll never conflict.