🐛 Configure esbuild-wasm initialize to use installed package version #5893
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.
Description
Configures esbuild-wasm’s initialize to load the WASM from a URL pinned to the installed package version, preventing mismatches between the JS wrapper and the WASM binary. Also upgrades esbuild-wasm to 0.25.10.
Problem
Using an unpinned
WASM
URL could fetch a different version than the installedesbuild-wasm
JS, causing runtime errors and version conflicts.Linked PR: #5865
Changes
Contribution checklist