Skip to content

Bump wasm-bindgen from 0.2.100 to 0.2.120#248

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/wasm-bindgen-0.2.120
Open

Bump wasm-bindgen from 0.2.100 to 0.2.120#248
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/wasm-bindgen-0.2.120

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 2, 2026

Bumps wasm-bindgen from 0.2.100 to 0.2.120.

Release notes

Sourced from wasm-bindgen's releases.

0.2.120

No release notes provided.

0.2.118

Added

  • Added Error::stack_trace_limit() and Error::set_stack_trace_limit() bindings to js-sys for the non-standard V8 Error.stackTraceLimit property. #5082

  • Added support for multiple #[wasm_bindgen(start)] functions, which are chained together at initialization, as well as a new #[wasm_bindgen(start, private)] to register a start function without exporting it as a public export. #5081

  • Reinitialization is no longer automatically applied when using panic=unwind and --experimental-reset-state-function, instead it is triggered by any use of the handler::schedule_reinit() function under panic=unwind, which is supported from within the on_abort handler for reinit workflows. Renamed handler::reinit() to handler::schedule_reinit() and removed the set_on_reinit() handler. The __instance_terminated address is now always a simple boolean (0 = live, 1 = terminated). #5083

  • handler::schedule_reinit() now works under panic=abort builds. Previously it was a no-op; it now sets the JS-side reinit flag and the next export call transparently creates a fresh WebAssembly.Instance. #5099

Changed

  • MSRV bump from 1.71 to 1.76 for the CLI, and 1.82 to 1.86 for the API #5102

Fixed

  • ES module import statements are now hoisted to the top of generated JS files, placed right after the @ts-self-types directive. This ensures valid ES module output since import declarations must precede other statements. #5103

  • Fixed two CLI issues affecting WASM modules built by rustc 1.94+. First, a panic (failed to find N in function table) caused by lld emitting element segment offsets as global.get $__table_base or extended const expressions instead of plain i32.const N for large function tables; the fix adds a const-expression evaluator in get_function_table_entry and guards against integer underflow in multi-segment tables. Second, the descriptor interpreter now routes all global reads/writes through a single globals HashMap seeded

... (truncated)

Changelog

Sourced from wasm-bindgen's changelog.

wasm-bindgen Change Log


Unreleased

Added

Fixed

  • Fix compilation failure with no_std + release #5134

Changed


0.2.119

Added

  • Added support for the wasm64-unknown-unknown target (memory64 / wasm64). usize / isize and raw pointers are now lowered through an f64 JS number ABI on wasm64 (matching the existing convention used for Option<u32> etc. on wasm32), with the CLI inspecting the module's memory type to pick the right codegen path. Includes a dedicated wasm64 CI job and test suite covering the new ABI paths. #5004

  • Promise ergonomics: Promise::all_tuple and Promise::all_settled_tuple for heterogeneous concurrent awaits (arity 1..=8, destructure via .into_tuple()), and a new wasm_bindgen::IntoJsGeneric trait underpinning typed-Array inference (with codegen-emitted identity impls and a #[wasm_bindgen(no_into_js_generic)] opt-out for types like JsClosure). Also re-exports JsGeneric from the prelude. Typed collection on js_sys::Array<T> is exposed as the inherent constructor Array::<T>::from_iter_typed (and companion extend_typed), inferring T from the iterator item via IntoJsGeneric. The stable FromIterator / Extend impls on Array (= Array<JsValue>) bound by AsRef<JsValue> are preserved, so existing .collect::<Array>() call sites keep compiling unchanged. Fixes #5042. #5121, #5125

  • Added wasm_bindgen::instance() to return the current WebAssembly.Instance. The generated JS glue retains the instantiated WebAssembly.Instance. #5118

  • Added a --cfg=wasm_bindgen_use_js_sys opt-in that makes async macro codegen use js_sys::futures instead of wasm_bindgen_futures, dropping the need

... (truncated)

Commits
  • 3c5043f Release 0.2.120 (#5131)
  • c68c40f release: 0.2.119 - schema bump (#5129)
  • a9f3fb6 Release 0.2.119 (#5126)
  • 17d783e Switch js-sys macro codegen opt-in from Cargo feature to cfg (#5127)
  • 33b1244 Restore stable AsRef<JsValue>-based FromIterator/Extend for Array; expose typ...
  • 208e874 Simplify web-sys generated bindings (#5122)
  • 3455345 Add wasm64/memory64 support for wasm64-unknown-unknown target (#5004)
  • 4c8fd1f Use js_sys::futures instead of wasm_bindgen_futures in codegen (#5112)
  • e82e693 Use Publish Environment (#5124)
  • 5727923 feat: Promise ergonomics for typed concurrent awaits (#5121)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels May 2, 2026
@dependabot dependabot Bot force-pushed the dependabot/cargo/wasm-bindgen-0.2.120 branch from 571829e to 1ae25b8 Compare May 4, 2026 06:51
Bumps [wasm-bindgen](https://github.com/wasm-bindgen/wasm-bindgen) from 0.2.100 to 0.2.120.
- [Release notes](https://github.com/wasm-bindgen/wasm-bindgen/releases)
- [Changelog](https://github.com/wasm-bindgen/wasm-bindgen/blob/main/CHANGELOG.md)
- [Commits](wasm-bindgen/wasm-bindgen@0.2.100...0.2.120)

---
updated-dependencies:
- dependency-name: wasm-bindgen
  dependency-version: 0.2.120
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/cargo/wasm-bindgen-0.2.120 branch from 1ae25b8 to 17462bf Compare May 4, 2026 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants