Paul Hawxby
Paul Hawxby
It may be because without a notification this is confusing, it just appears to not work. 
Yeah, I toyed with that idea but haven't got around to writing anything to do it yet. I think if/when I get time I'll write a core feature and PR...
Nothing from me, just too damn busy at the moment
Is there anything I can do to get this PR moving along again? We generally try to avoid falling too far behind even minor versions
> @phawxby nothing new since the last activity, feel free to fix: [#12205 (comment)](https://github.com/facebook/jest/pull/12205#discussion_r815307518) As you noted in the thread above, the `importModuleDynamically` issue could be a different bug. Would...
> > > @phawxby nothing new since the last activity, feel free to fix: [#12205 (comment)](https://github.com/facebook/jest/pull/12205#discussion_r815307518) > > > > > > As you noted in the thread above, the...
A bit more digging and I've found this, which suggests this isn't going to be especially easy to fix. https://github.com/nodejs/node/issues/25424#issuecomment-770216256 Which then ties in with this. https://bugs.chromium.org/p/v8/issues/detail?id=12198
@backmask @SimenB I've found the problem and now I've seen it 🤦 I'm writing some more/better tests to try and catch this in future and should have the PR ready...
PR is mostly done and I solved a few other bugs that I found while I was at it. I'm nos just trying to resolve the Windows weirdness that doesn't...
Source of the problem narrowed down on Windows. The child process appears to be crashing as it's forked but I don't know why just yet. Obviously this is only happening...