Allow configuration objects in "projects"

[azz]

Do you want to request a feature or report a bug?

Feature.

---

A pattern I have been repeating recently is using the "projects" feature to run many runners in the same build. To do this I do:

package.json:

{
  "jest": {
    "projects": ["jest.*.config.js"]
  }
}

jest.eslint.config.js:

module.exports = {
  runner: "jest-runner-eslint",
  displayName: "lint",
  // ...
};

jest.test.config.js:

module.exports = {
  displayName: "test",
  // ...
};

This all works fine but it is a bit annoying having three config sources. What I propose is the ability to pass configuration objects instead of paths in the "projects" array.

For example, we could express all three of the above configuration components with one file:

jest.config.js:

const lint = {
  runner: "jest-runner-eslint",
  displayName: "lint",
  // ...
};

const test =  {
  displayName: "test",
  // ...
};

module.exports = {
  projects: [lint, test]
}

[SimenB]

I like it 🙂 Would make custom runners even easier to use, and your example of an easy way of doing lint and test together seems really compelling for Jest as more than a test runner (combined with presets and we're really getting places).

Would you be able to create a PR for it?

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.