feat(js): improve SWC compilation error logging #33297
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds clearer diagnostics when SWC compilation fails: - logs Error.message - prints stderr and stdout outputs Improves debugging for local development and CI.
👷 Deploy request for nx-docs pending review.Visit the deploys page to approve it
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when SWC compilation fails, Nx logs only a generic message:
"SWC compilation failed"
There is no
error.message, nostderrand nostdoutprinted.In many cases the actual cause of failure is completely hidden, which makes debugging very difficult, especially in CI.
This PR improves the logging by printing:
This makes SWC failures visible and debuggable again.
Current Behavior
Only a generic "SWC compilation failed" message is logged. No error message or stdout are shown.
Expected Behavior
Include error.message, stderr, and stdout (when available) so developers can understand and debug failures.