fix: rethrow astroerrors in image processing #13407
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.
Changes
If Astro detects that sharp is not installed when trying to transform an image it will throw a
MissingSharperror. However when this happens during a build, we currently catch it and instead throw aCouldNotTransformImageerror, with a message suggesting the image is corrupt. The correct error is buried in thecause. This PR checks if the thrown error is an AstroError, and if so rethrows it rather than throwing aCouldNotTransformImageerror. This means that theMissingSharperror is logged correctly.Testing
Tested manually
Docs