Simen Bekkhus
Simen Bekkhus
Yeah, the envs are the ones that construct the `global` used in tests, so it makes sense that they have it. Doesn't mean it's a nice pattern, though 😀 Due...
Note that you'll never be able to share things that are not json-serializable as we have no way of passing that to workers. But sharing e.g. URLs to services will...
No, that's not how communication between processes work: https://nodejs.org/api/child_process.html#child_process_subprocess_send_message_sendhandle_options_callback It's a bit better with worker_threads for builtin primitives, but not much: https://nodejs.org/api/worker_threads.html#worker_threads_port_postmessage_value_transferlist --- This isn't an API choice Jest has...
I don't know in how many ways I can say this, but I'll try one last time: you _cannot_ pass around instances, it's not possible. And seeing as this issue...
New release is out: https://github.com/facebook/jest/releases/tag/v24.6.0
> These test failures don't appear to be related to my changes, are they known to be flaky? Yeah, at times 😞 I restarted the failing builds now
https://github.com/facebook/jest/releases/tag/v29.0.0-alpha.5
> Ah, it appears to be this change. #13036 Yep. https://jestjs.io/docs/next/upgrading-to-jest29#snapshot-format
Yep, that's the plan! Mostly waiting for a resolution on #12856
Thanks @snitin315!