Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Errors shouldn't be hidden by catches #497

Closed
chrisportela opened this issue Sep 10, 2015 · 2 comments
Closed

Errors shouldn't be hidden by catches #497

chrisportela opened this issue Sep 10, 2015 · 2 comments

Comments

@chrisportela
Copy link

I've been debugging issues in migrating to Node v4.0.0 and the errors that Jest has sometimes are just horrible and hide information I could use. Like knowing which file the error is happening in case I need to update that one or not.
@cpojer
Copy link
Member

cpojer commented Sep 10, 2015

This was fixed in 0.5.3, let me know if this is still broken for you.

@cpojer cpojer closed this as completed Sep 10, 2015
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cpojer @chrisportela