fix: Error Handling and Improvements in File Deletion Process #5396
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.
I’ve made a few updates to improve the stability and clarity of the file deletion script. The most significant change is the addition of error handling using
try...catch
, which will prevent the script from failing unexpectedly when deleting files. Additionally, I’ve updated thefs.readFileSync()
method by specifying theutf8
encoding to ensure the file is read as text, avoiding potential encoding issues.The message logged when deleting files has also been updated to specifically reference "build artifacts" rather than just "files," which provides clearer context.
These improvements should help avoid errors during the file removal process and enhance the script's overall reliability.
PR Checklist
npx changeset add
)