-
Notifications
You must be signed in to change notification settings - Fork 458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clearImmediate is not defined
error when using new v7.29.5 via cypress
#899
Comments
clearImmediate is not defined
error when using dom-testing-library via cypressclearImmediate is not defined
error when using new dom-testing-library v7.29.5 via cypress
clearImmediate is not defined
error when using new dom-testing-library v7.29.5 via cypressclearImmediate is not defined
error when using new v7.29.5 via cypress
Thanks for the report. Could you try if this still happens with If the issue persists then we would need a reproduction to debug the issue. A link to a repository on GitHub, or provide a minimal code example that reproduces the problem. Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve |
Hello, I had a similar issue and I confirm that by upgrading Thanks for the fix ! |
Waiting for @kschiffer to confirm or if there's no response within 7 days. |
I can confirm that the issue is resolved. Thanks for the swift action and for this awesome library <3. |
@testing-library/dom
version: 7.29.5Cypress Chrome 88
Relevant code or config:
Running any cypress test that uses
@testing-library/cypress
.What you did:
Running cypress tests which worked before the update.
What happened:
Reproduction:
Running any cypress test that uses
@testing-library/cypress
.Problem description:
The error originates from here: ac9a6b7#diff-49ba0c85360693b8e89ae0e0428284a55db749f08f2b9993d26910def646e02fR13
It appears like
dom-testing-library
assumes thatclearImmediate
andsetImmediate
are globally available, but it appears to be available in Internet Explorer 10 only.Suggested solution:
I don't have time to look into why
setImmediate
is used in the first place, but I suppose thatsetImmediate
needs to be removed or at least polyfilled beforedom-testing-library
uses it in the global scope.The text was updated successfully, but these errors were encountered: