Add an option for config file path in package.json

[DavidBabel]

🚀 Feature Proposal

For now, when we want to configure jest we have three choices :

• put the jest config in package.json
• put the jest config in jest.config.js at root
  In both this previous choices, you can easily run your tests with a simple jest command.
• put the jest config in whatYouWant.js anywhere in your project
  With this last choice you have to run jest -c ./path/to/whatYouWant.js

Motivation

The idea is to run a simple jest command in any of the three cases.

Example

The idea should be to add a new option in package.json. It may be something like defaultConfigFile:

{
  "name": "myModule",
  "jest" : {
    "defaultConfigFile": "./path/to/whatYouWant.js"
  }
}

In this case, it's the only option in package.json, which override the default config file search at root. The rest of the config stays in your whatYouWant.js

Pitch

Why does this feature belong in the Jest core platform?

Because it's a native configuration proposal.

[SimenB]

Having config be able to reside in configuration and not just in code seems reasonable to me.

Linking in #7185

[DavidBabel]

Thanks

[carlosm2011]

Has this been implemented yet?

[lk77]

Hello,

any news on this ?

my jest config file is not in the root directory but inside tests/unit, and it's annoying.

[D-Pow]

For me, adding the preset field to my package.json seems to have worked to do exactly that. It made my custom config file globally accessible for all npm scripts as well as IDE-initiated tests, which previously used to fail unless I manually specified where jest.config was located.

"jest": {
  "preset": "./config/jest/jest.config.mjs"
}

[Turbotailz]

Thanks @D-Pow this was exactly what I needed to get WebStorm to use my config for default run configurations

[DavidBabel]

Thanks @D-Pow for the hint. I resolve this issue.

[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.