chore: use @jest/globals instead of @types/jest

[mrazauskas]

Pull Request

Problem

The @types/jest is redundant, because Jest ships typings via @jest/globals package. (By the way, Jest repo has type tests with more than 1000 assertions.)

Main difference: testing APIs must be explicitly imported from @jest/globals, instead of being globally available. This means that in a way @types/jest is polluting the global namespace. For instance, currently it is possible to use Jest's test() helper in type tests. That does not sound right, or?

Solution

Replaced @types/jest with imports from @jest/globals.

ChangeLog

N/A

[shadowspawn]

I had this on my wish-list to look into. Some related references:

• https://jestjs.io/docs/getting-started#using-typescript
• https://jestjs.io/blog/2020/05/05/jest-26#a-new-way-to-consume-jest---jestglobals
• [new-rule] prefer importing from @jest/globals jest-community/eslint-plugin-jest#1101

[shadowspawn]

Looks good apart from setting for injectGlobals.

[shadowspawn]

LGTM, thanks