config.presets as an array

🚀 Feature Proposal

Allow jest configuration file to include an array of presets, on top of a module/file path.

Motivation

When adding multiple presets, the only solution we have is messy: deep concatenation of properties.

Example

export default {
  preset: ["ts-node", "webdriverio"]
}

Pitch

This deserves to make it into the core because it goes alongside what jest does well in its’ configuration: intuitive customisability. We support other properties like projects, so I think that this deserves the same level of concern.

Out of Scope

Jest is awesome, it feels very good to use!

[waynevanson]

@sigveio I would say that documentation is the better alternative. I think you’re right, it’s a bit complicated.

Would you be happy a more polished version of this below?

---

A preset is a jest configuration, so feel free to import and merge it into to create custom configurations. This is useful when there are multiple presets, and provides flexibility if there are conflicts between common properties (ie Multiple Reporters or Transformers).

With ts-node and cjs examples.

import { default as TsJest } from "ts-jest"

export default {
  ...TsJest,
  // ... other configuration
}

[github-actions[bot]]

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.