fix(core): show better errors #29525
Open
+54
−48
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
JamesHenry
requested changes
Jan 6, 2025
AgentEnder
force-pushed
the
fix/show-better-errors
branch
from
326d9b0 to
65466a2
Compare
|
View your CI Pipeline Execution ↗ for commit 9ed7de2.
☁️ Nx Cloud last updated this comment at |
JamesHenry
approved these changes
Jan 8, 2025
AgentEnder
force-pushed
the
fix/show-better-errors
branch
from
65466a2 to
9ed7de2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Current Behavior
Sub-errors are hidden when any project graph error is encountered. This is detrimental, as things like "missing comma in JSON" get hidden and make people think that Nx is broken, when in fact their config files are invalid.
Expected Behavior
Sub errors are shown regardless of verbose logging (but including their stack trace if verbose logging is enabled)
Without Verbose
With Verbose
Related Issue(s)
Fixes #