Simen Bekkhus
Simen Bekkhus
https://github.com/facebook/jest/releases/tag/v29.0.3
Hmm, still an issue @mrazauskas ``` node_modules/@jest/environment/build/index.d.ts:330:26 - error TS2430: Interface 'JestImportMeta' incorrectly extends interface 'ImportMeta'. The types returned by 'jest.clearAllTimers()' are incompatible between these types. Type 'void' is not...
I guess there's not much we can do here? We could possibly move our `ImportMeta` declaration?
Nah, it should definitely _be_ there, but it's annoying when the types clash. So I meant to move our own to a place it doesn't clash with the `@types/jest` definition....
Ah nice! Would be awesome to align - makes it easier to make their types based on ours in the future 👍
@mrazauskas after that's released, can we add a type test here that we're compatible? ```ts import {jest as realJest} from '@jest/globals'; expectAssignable(realJest); ``` or something like that? Of course that...
does it work with https://github.com/facebook/jest/releases/tag/v29.1.0?
could you rebase?
>In its simplest form this shifts jest usage from relying on globals to explicitly imported functions That's already possible via `@jest/globals`: https://jestjs.io/blog/2020/05/05/jest-26#a-new-way-to-consume-jest---jestglobals (the typescript caveat is no longer true: https://jestjs.io/docs/next/expect#expectextendmatchers)...