You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@kentcdodds Just stumbled on this - Thanks for fixing this! FYI: I just filed jestjs/jest#10555 to hopefully get jest to provide an official way to find out if fake timers are being used. Just referencing this here so if the API is added there, appropriate changes can be made.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What: microtask flushing now supports fake timers
Why: So people can use fake timers in their react tests without it causing issues with React's scheduler
How:
Checklist:
- [ ] Documentation added to the docs siteN/A- [ ] TestsN/A (really really hard to reproduce)- [ ] Typescript definitions updatedN/A