Carl-Erik Kopseng
Carl-Erik Kopseng
@3lang3 Do you use the same Node versions on both platforms? I see the original issue is using Node 14 which is not a supported LTS release anymore.
I guess this is the classic case of "you're screwed if you do, and screwed if you don't" 😄 I was more or less expecting the fallout of this change...
**Another option: we could revert this change** Meaning we skipped `nextTick` and `setImmediate` to be friendlier for the most common case. The underlying library, `fake-timers`, seems to be _mostly_ used...
Everything I have tries reports 0. This has been broken almost since launch.
Thanks for this, I will have to check out the code at a later time. > testers are always forced to write tests with intimate knowledge of when the mock...
Sorry about that. Was hoping someone else on the maintainer team would pick it up, and I have simply forgotten about it 😄 I will have a new look tomorrow...
@atscott Hi, Scott. Seeing this hanging for such a long time is embarrassing, but I have almost not been touching JS for the last six months, so it's been hard...
I have forgotten about this, so this was a great reminder. I stopped for the same reasons that Andrew Asked about: I was uncertain about the order and correctness. @Uzlopak...
This has had enough time to mature and enough eyes on its that I feel somewhat OK in merging this. Even if I don't understand it fully 🙈 The test...
@dependabot recreate