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.

JSDOM error handling

See original GitHub issue

Is there any way to make JSDOM forward script errors to Node.js?

I assumed the following would log undefined has no method 'toString' but the errors are null:

jsdom.env(
  '<html><script>nonExistentVariable.toString()</script></html>'
, []
, function (errors, window) {
    console.log(errors)
  }
)

Issue Analytics

State:
Created 10 years ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

domeniccommented, Jan 22, 2014

You are sending the messages to the window’s console, but that is different from the Node.js console. Try this instead:

var document = jsdom('<!DOCTYPE html> <script>window.errors = [];' +
  'window.onerror = function (message) { window.errors.push(message); };' +
  'nonExistentVariable.toString();</script>');

console.log(document.parentWindow.errors);

0reactions

SystemParadoxcommented, Apr 5, 2016

In case this helps anyone else, in 3.1.1 I had to add the following to forward errors from event scripts (otherwise they go silently unnoticed):

document.raise = function (type, message, data) {
    if (data.error) {
        throw data.error;
    } else {
        console.error('ERROR', message);
    }
};