chore(jest-cli): Deprecation of the --init argument#14490
chore(jest-cli): Deprecation of the --init argument#14490SimenB merged 7 commits intojestjs:mainfrom
--init argument#14490Conversation
✅ Deploy Preview for jestjs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@SimenB could you please add it to the Jest 30 Milestone? |
--initargument--init argument
--init argument--init argument
|
We should handle people passing it and direct them to the new command. Currently AFK, but grep-ing for |
|
Around here: jest/packages/jest-validate/src/validateCLIOptions.ts Lines 107 to 109 in 0b0cf73 So possibly just adding to https://github.com/jestjs/jest/blob/0b0cf73a9fd5d6ad6cbf0152da0caed3658874b7/packages/jest-config/src/Deprecated.ts |
Thanks @SimenB, I'm already trying that, the only thing that is left is that we need to keep that in Another thought is that we probably need to exit early, because this deprecation message is only a warning, and it will try to run
|
|
I'd suggest to update It will make deprecation logic more flexible, otherwise we need to keep unnecessary code for a while |
That makes sense to me 👍 Wanna send a separate PR for that? Should be landable in 29 |
Sounds good |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |

Summary
As discussed here I prepared a PR for Jest 30 with the deprecation of the
--initflagTest plan
I checked that: