Simen Bekkhus
Simen Bekkhus
@EvHaus Traces from JSDOM is interesting (might also be completely coincidental, of course). Could you try installing `jest-environment-jsdom@24` and using that? We upgraded from 11 to 15, so something in...
Interesting! If you have time, it'd be lovely if you could test - https://www.npmjs.com/package/jest-environment-jsdom-twelve - https://www.npmjs.com/package/jest-environment-jsdom-thirteen - https://www.npmjs.com/package/jest-environment-jsdom-fourteen Or just link in `jsdom` and bisect. I'll do that tomorrow, but...
Essentially same underlying issue here the solution I suggest in https://github.com/facebook/jest/issues/9881#issuecomment-1050671577 - `expect` is not bound to a single test, and maintains a global state. So async will confuse it....
Yeah, I wanna add that type of API. Unfortunate we used the `test` name as just an alias for `it` instead of breaking teh API 😅 FWIW I'd me 100%...
FWIW, I think it's a good idea to distribute a "full" name version. Like `yarn` is both `yarn` and `yarnpkg`. But that doesn't really solve the underlying issue
> > if someone installed 🚂 two years ago and forgot about it, it’s going to be really hard for them to figure out why their test runner is broken...
We really should strip out the ansi codes somehow 😅 Is the flake only for 21.3, or does it also happen for v18 and v20?
Installing the nightly is probably easier than building from source, FWIW 🙂
Never heard of volta, but: https://nodejs.org/download/nightly/
This needs to upgrade npm on Ci seemingly