-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: breaking behavior for TypeScript globals compared to the DefinitelyTyped counterpart #12853
Comments
I think a solution to go is doing like |
Global types are not defined by any modules in this repo, they are in DT. (I realize the name of the module in Jest is bad). @ahnpnl seems somewhat reasonable way of opting into global types. We don't have global types in this repo tho. Might make sense to add in the same way, but that's separate from this issue. Could you open up a feature request for it instead? |
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. |
Version
28.1.0
Steps to reproduce
Expected behavior
I expect that importing
@jest/globals
would indeed add common things likedescribe
,it
,test
,beforeEach
, etc. to the global scope, so I don't have to import them every time explicitly:Actual behavior
I'm seeing TSC errors like these on an attempt to compile my test suites:
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: