Fix PackageToJS plugin wasm-opt fallback when output file exists #401
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.
Fixes a bug where PackageToJS builds fail when wasm-opt is not installed and the output file already exists.
The plugin falls back to copying the input file when wasm-opt is unavailable, but FileManager.copyItem throws an error if the destination exists. This causes "File exists" build failures.
The fix removes any existing output file before copying, matching wasm-opt's overwrite behavior. Also makes DefaultPackagingSystem injectable for cleaner testing.