-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
throw undefined
turns into a TypeError: Cannot read property 'message' of undefined
#3183
Comments
If this is an important use case for you, could you submit a pull request to fix the function in the backtrace to deal better with jsdom/lib/jsdom/living/helpers/runtime-script-errors.js Lines 38 to 39 in 04f6c13
|
Thanks for the quick reply. I'm not familiar with the jsdom code, but I can take a stab at it. |
Published in 16.6.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basic info:
Minimal reproduction case
result:
How does similar code behave in browsers?
Why is this important?
We're trying to test a React component that throws
undefined
and is caught by an error boundary. But instead of the error boundary seeingundefined
, it sees anError
with a message ofCannot read property 'message' of undefined
.The text was updated successfully, but these errors were encountered: