`deprecationEntries` should be injected from `jest-validate` from `jest-config`.

Do you want to request a feature or report a bug? I guess it’d be a feature.

What is the current behavior? jest-validate requires jest-config to get the deprecationEntries function. This means consumers of jest-validate also have to install all the dependencies of jest-config, such as jest-environment-jsdom.

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.

What is the expected behavior? jest-validate should contain deprecationEntries.

Please provide your exact Jest configuration

Run npx envinfo --preset jest in your project directory and paste the results here

[SimenB]

jest-validate should definitely be able to drop the jest-config dependency. PR very much welcome for this 🙂 I agree with @thymikee that it should be injected as a separate argument instead of living inside jest-validate.

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