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
We have a yarn monorepo and run the build step as follows:
"build": "wsrun --stages --fast-exit --collect-logs --report build:packagr ",
If one one the modules fails we see in a report what module failed but not why, the error output of the failing module is lost. All we see is:
1 packages finished `build:packagr` with error: @prod-publishing-react/block-settings
If we then just run the build command for the failing package again via yarn, e.g. like:
yarn workspace @prod-publishing-react/block-settings build:packagr
we see the reason for the failure on stderr.
Question: how can we make sure to see the stderr of a failing module when using wsrun?
The text was updated successfully, but these errors were encountered:
I'm seeing the same thing. Removing --collect-logs causes the error output to appear, but the output overall is less nice.
--collect-logs
Sorry, something went wrong.
No branches or pull requests
We have a yarn monorepo and run the build step as follows:
If one one the modules fails we see in a report what module failed but not why, the error output of the failing module is lost. All we see is:
If we then just run the build command for the failing package again via yarn, e.g. like:
we see the reason for the failure on stderr.
Question: how can we make sure to see the stderr of a failing module when using wsrun?
The text was updated successfully, but these errors were encountered: