We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here is a complete, minimal reproduction executed on Github Actions. https://github.com/cspotcode/repros/tree/node-source-map-worker-thread
new Error().stack
Always.
Sourcemap information is included in a stack trace within a worker_thread if that information is included in the stack traces in the main thread.
Worker thread stacks do not include sourcemap information even though main thread stacks do.
The text was updated successfully, but these errors were encountered:
This problem seems to be fixed on the master branch. But it's not fixed on the latest release(v14.9.0).
Sorry, something went wrong.
Still broken in v14.16.0, even explicitly setting execArgv doesn't help.
v14.16.0
execArgv
Works in 14.17.3
14.17.3
Can confirm, 14.17.3 became available on CentOS 8, and no longer exhibits the problem.
I'll close, assuming this is fixed. Feel free to ask to reopen if it's not the case.
No branches or pull requests
What steps will reproduce the bug?
Here is a complete, minimal reproduction executed on Github Actions.
https://github.com/cspotcode/repros/tree/node-source-map-worker-thread
new Error().stack
within the worker_thread. See that the stack does not have sourcemap information.How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
Sourcemap information is included in a stack trace within a worker_thread if that information is included in the stack traces in the main thread.
What do you see instead?
Worker thread stacks do not include sourcemap information even though main thread stacks do.
Additional information
The text was updated successfully, but these errors were encountered: