fix: Remove truncation of preprocessor errors #15198
Merged
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.
User facing changelog
Additional details
We used to remove the stack from where there was a preprocessor error. I don't remember why. It may have been that we thought the error was overly verbose when we displayed it. But removing the stack makes it very difficult to debug a preprocessor, so it's better if we keep it and err on the side of it being verbose.
How has the user experience changed?
Users now see the error stack when there's a preprocessor error.
Before
After
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?