fix: make no-jest-import error message more accurate

[mmkal]

It isn't quite accurate to say that Jest doesn't export anything. It exports the run and runCLI functions, even though it isn't generally recommended to use them (yet).

This updates the message to match the language in https://jestjs.io/docs/jest-object ("The jest object is automatically in scope within every test file").

There's also a similar update to the no-jest-import.md docs file.

[SimenB]

I'm fine with either wording, @G-Rath wdyt?

[G-Rath]

tbh I think we should be tossing the rule all together as it's no longer accurate:

• require('jest') doesn't give you an object with the same properties as what most people want (e.g. test, spyOn, fn, etc) so it should be very obvious something wrong is being done
• now that we have @jest/globals, it is valid to import jest from there (and my understanding is that's required in ESM)
• you can use no-restricted-imports to enforce @jest/globals isn't used, and you can set injectGlobals to false to enforce using @jest/globals
  • though we want a new rule that enforces using @jest/globals (tracked by [new-rule] prefer importing from @jest/globals #1101, and should be coming soon)

That middleone at least means the proposed new message isn't actually true, because it depends on if you have injectGlobals set.

[github-actions]

🎉 This issue has been resolved in version 27.0.0-next.2 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 27.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀