Simen Bekkhus
Simen Bekkhus
Main reason is that this will make it much worse for node 12 and 14, and it's really a bug in node
I don't think we should add a config flag - if we do this we should just detect the version of node inline so people don't have to change anything....
@phawxby nothing new since the last activity, feel free to fix: https://github.com/facebook/jest/pull/12205#discussion_r815307518
Instead of using a patch, one thing that can be done is to extend the default `jest-runtime` and override `_execModule`. It can be passed as `runtime` in configuration (renamed from...
This sounds like it can just be a custom reporter. Or possibly configuration for the built in reporters?
Having a small repro would be great
Is this just happening on Windows? I don't have access to windows machines beyond virtual machines, so not the easiest to debug for me... @jeanlauliac you added `write-file-atomic` in #4088,...
Would it be possible to create a repro showing that just using `write-file-atomic` in `worker-farm` against the same file fails somehow? Would be great to open an issue against that...
>Well, firstly the issue should not even happen when `--no-cache` is on, since the cache should not be populated. That's a good point, and should be fixed separately. That way...
>I'd like to retain that. New flag? It's a highly misleading name. And on e.g. CI you rarely want the cache anyways, so it's just wasted resources. Or is a...