Repository navigation
chore(wasm): upgrade wasm-bindgen 0.2.100 -> 0.2.129 - #792
Merged
Merged
Conversation
Newer glue no longer emits the newnoargs import (new Function(...)) that the community directory scan flags as Dynamic Code Execution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Moves the exact pin in
wasm/Cargo.tomlfrom=0.2.100to=0.2.129(plus matchingjs-sys/wasm-bindgen-test) and regenerateswasm/pkg.The newer glue no longer emits the
__wbg_newnoargsimport (new Function(...), from js-sys'sglobal()fallback), which the community directory scan reports as Dynamic Code Execution.main.jsnow contains noeval/new Function..d.tsAPI unchanged apart from an internal table rename (__wbindgen_export_2->__wbindgen_externrefs)..wasm+12 KB (322 -> 334 KB).wasm:test, build, 402 tests, lint; live graph build and trail traversal in the dev vault.