Add a `--node-arguments` flags

[GMartigny]

Description

It could be useful to be able to de define the flags of the Node process running AVA. A comment by @novemberborn scratch the surface, but apparently it never got raised as a request.
Any compatible Node flag could be listed.

Adding the --nodeArgs``--node-args--node-arguments to AVA could allow the user to execute Node with some needed flags.
(eg: ava --node-arguments --experimental-report)
It should also be available as an AVA config property:

{
  "ava": {
    "nodeArguments": [
      "--experimental-report",
      "- --custom-arg"
    ]
  }
}

Test Source

process.execArgv.includes("--experimental-policy"); // <= Never true

Environment

• Ubuntu v16.04
• Node v11.9.0
• AVA v1.4.1

---

IssueHunt Summary

maximelkin has been rewarded.

Backers (Total: $60.00)

• issuehunt ($60.00)

Submitted pull Requests

• #2272 Allow Node arguments to be configured

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[novemberborn]

Thanks for opening this, @GMartigny. Should it be --node-args though?

[GMartigny]

@novemberborn, yes you're right since --update-snapshots and --reset-cache are kebab-case.

[sindresorhus]

I would prefer --node-arguments. You don't really gain much from shortening it.

It should also be possible to set it as a AVA config property.

[GMartigny]

It should also be possible to set it as a AVA config property

As a string, an array or both ?

[novemberborn]

It should also be possible to set it as a AVA config property

As a string, an array or both ?

Array.

Are there use cases for specifying these flags as a one-off when you run AVA through the CLI, or should we only support them as a config property, since you'd want to use them all the time?

[sindresorhus]

I would say both. For example, you get a warning that you're using a deprecated Node.js API, but it doesn't show a stack trace, so you need to pass in a certain CLI argument to Node.js to force it to show where the warning came from. You only need that once.

[GMartigny]

Are there use cases for specifying these flags as a one-off when you run AVA through the CLI

Off the top of my head, I see a difference between running test locally and through CI. Maybe for environment purpose too like no having the same flags on different node versions.

[IssueHuntBot]

@IssueHunt has funded $60.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.