feat(js): improve SWC compilation error logging#33297
Merged
Coly010 merged 1 commit intonrwl:masterfrom Dec 12, 2025
Merged
Conversation
👷 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.
|
Coly010
approved these changes
Dec 12, 2025
Adds clearer diagnostics when SWC compilation fails: - logs Error.message - prints stderr and stdout outputs Improves debugging for local development and CI.
Contributor
|
View your CI Pipeline Execution ↗ for commit e5e852f
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
pushed a commit
that referenced
this pull request
Dec 15, 2025
Currently, when SWC compilation fails, Nx logs only a generic message: "SWC compilation failed" There is no `error.message`, no `stderr` and no `stdout` printed. 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: - error.message (or the error itself) - stderr if available - stdout if available 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. (cherry picked from commit 54eed65)
FrozenPandaz
pushed a commit
that referenced
this pull request
Dec 15, 2025
Currently, when SWC compilation fails, Nx logs only a generic message: "SWC compilation failed" There is no `error.message`, no `stderr` and no `stdout` printed. 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: - error.message (or the error itself) - stderr if available - stdout if available 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.
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.