OK, after a short binary search, I have tracked my issue down to jsdom
>=v0.2.11
I don't see anything that stands out in the changelog that would cause
your issue, but you could try 'npm install -g jsdom@0.2.10' and see if
your issue goes away.
Diving into jsdom to see if I can find and fix my pr
I am also running jsdom, and have been seeing an old error pop back -
the jsdom script executor is throwing 'ReferenceError: navigator is
not defined' nearly every script I execute.
I suspect this is on node.js' end, but I am still digging. The reason
I post here is that I also saw this after a v
How can I tell if the script is being executed via jsdom? I assumed it
was node but wanted to be sure.
I'll need to look into this a bit more to verify if this is a jsdom
issue or something related to node itself
Thanks for the in-depth answer!
Toran
On Apr 25, 7:24 pm, Elijah Insua wrote:
> O
