Support arguments in "require" configuration

[novemberborn]

Prompted by #1665 and inspired by Babel's plugin / preset configuration, it'd be neat to do this:

"ava": {
  "require": [
    ["@babel/register", {
      "ignore": ["test/*"]
    }]
  ]
}

If an array is provided we'd require the module, resolve any __esModules / default shenanigans, and invoke .apply() with the remaining values. We should support any number of arguments.

---

IssueHunt Summary

sculpt0r has been rewarded.

Backers (Total: $40.00)

• issuehunt ($40.00)

Submitted pull Requests

• #3184 feat: handle complex options.require config property

---

Tips

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

[Jolo510]

Hey @novemberborn, I'd like to take on this task!

[novemberborn]

@Jolo510 awesome, go for it!

[anayaml]

Hey, @novemberborn, I'd like to work on this task

[novemberborn]

@amslv awesome, thanks!

Since this issue was opened, we added support for ava.config.js files. We need to make sure the arguments can be stringified as JSON and then parsed in the worker processes.

We could do the stringifying and the parsing in the main process first, and then use our "deep equal" logic to make sure the values are the same:

ava/lib/assert.js

Line 282 in 6d12abf

const result = concordance.compare(actual, expected, concordanceOptions);

[IssueHuntBot]

@IssueHunt has funded $40.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.