-
Notifications
You must be signed in to change notification settings - Fork 223
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
Empty log lines on worker error #268
Comments
addaleax
added a commit
to addaleax/node-source-map-support
that referenced
this issue
Apr 19, 2020
Node.js Worker threads don’t handle `uncaughtException` the same way that the main thread does. The shim does not apply/make sense here, but breaks error handling support in unexpected ways instead. Fixes: evanw#268 Fixes: TypeStrong/ts-node#945
addaleax
added a commit
to addaleax/node-source-map-support
that referenced
this issue
Apr 19, 2020
Node.js Worker threads don’t handle `uncaughtException` the same way that the main thread does. The shim does not apply/make sense here, but breaks error handling support in unexpected ways instead. Fixes: evanw#268 Fixes: TypeStrong/ts-node#945
Fixed in version |
bestlucky0825
pushed a commit
to bestlucky0825/node-source-map-support
that referenced
this issue
May 30, 2022
Node.js Worker threads don’t handle `uncaughtException` the same way that the main thread does. The shim does not apply/make sense here, but breaks error handling support in unexpected ways instead. Fixes: evanw/node-source-map-support#268 Fixes: TypeStrong/ts-node#945
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please see TypeStrong/ts-node#945
The text was updated successfully, but these errors were encountered: