chore(jest-cli): Deprecation of the --init argument

[dj-stormtrooper]

Summary

As discussed here I prepared a PR for Jest 30 with the deprecation of the --init flag

Test plan

I checked that:

• jest prints deprecation error with corresponding message
• build doesn't contain any related code

[netlify]

✅ Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	17abf40
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/65095c67c972070008662c20
😎 Deploy Preview	https://deploy-preview-14490--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dj-stormtrooper]

@SimenB could you please add it to the Jest 30 Milestone?

[mrazauskas]

Thanks!

[SimenB]

We should handle people passing it and direct them to the new command. Currently AFK, but grep-ing for deprecated or some such should turn up some results.

[SimenB]

Around here:

jest/packages/jest-validate/src/validateCLIOptions.ts

Lines 107 to 109 in 0b0cf73

	if (deprecatedOptions.length) {
	logDeprecatedOptions(deprecatedOptions, CLIDeprecations, argv);
	}

So possibly just adding to https://github.com/jestjs/jest/blob/0b0cf73a9fd5d6ad6cbf0152da0caed3658874b7/packages/jest-config/src/Deprecated.ts

[dj-stormtrooper]

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 allowedOptions in order to make this message printed, because unrecognizedOptions check runs before the deprecation check
https://github.com/jestjs/jest/blob/main/packages/jest-validate/src/validateCLIOptions.ts#L86

Another thought is that we probably need to exit early, because this deprecation message is only a warning, and it will try to run jest after validation:

[dj-stormtrooper]

I'd suggest to update validateCLIOptions function to run deprecation warnings before other checks

It will make deprecation logic more flexible, otherwise we need to keep unnecessary code for a while

[SimenB]

I'd suggest to update validateCLIOptions function to run deprecation warnings before other checks

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

[dj-stormtrooper]

That makes sense to me 👍 Wanna send a separate PR for that? Should be landable in 29

Sounds good

[github-actions]

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

[SimenB]

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.1