Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Transactions/Cursors fail with `jsdom`
See original GitHub issueWith jsdom environment in jest@27 acting on a transaction after allowing other code to run (per await) throws errors.
This differs from executing the same calls in a node environment.
Maybe this is related to #64
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Issues with latest version of jest with the jsdom environment #64
Hey, Recently, the jest folks removed setImmediate and clearImmediate from the jsdom environment (they had it before incorrectly).
Read more >Node.js jsdom error - Stack Overflow
I have checked if the page is fetched and if the jquery lib is parsed - they are. We could look at the...
Read more >jsdom - npm
jsdom. jsdom is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js.
Read more >LinkeDOM: A JSDOM Alternative - Andrea Giammarchi
A battle tested module able to crash the program, or one that's so greedy optimizing stuff, that fails through its own inner optimizations?...
Read more >Testing with Node, Jest, and JSDOM - Manning Publications
Try executing it with node main.js and Node will immediately tell you that it has found a ReferenceError because “window is not defined.”...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ath0mas I’m running into some test timeout issues too; I opened #69 with my findings so far.
@ath0mas Do you have fake timers in place that might need to be advanced so that the calls to
setTimeoutin https://github.com/dumbmatter/fakeIndexedDB/commit/17c15473e0dd61a32240431573d21a1b4f5b150e are resolved?