Fix script error handling in CreateFileOperation #29
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.
When a file resource script fails (non-zero exit code or command not found), the raw execa error was propagating instead of being converted to a proper CommandExecError. This made it difficult to identify build failures.
Added try-catch around script execution to convert execa errors to CommandExecError with exit code and stderr message, consistent with ExecuteLocalCommandOperation.