85 releases

0.4.50 Jan 12, 2025
0.4.49 Dec 7, 2024
0.4.47 Nov 30, 2024
0.4.42 Mar 4, 2024
0.3.5 Nov 12, 2018

#86 in Asynchronous

Download history 923966/week @ 2024-11-05 921290/week @ 2024-11-12 895496/week @ 2024-11-19 777535/week @ 2024-11-26 931517/week @ 2024-12-03 1005871/week @ 2024-12-10 819702/week @ 2024-12-17 424494/week @ 2024-12-24 582601/week @ 2024-12-31 1068468/week @ 2025-01-07 1158764/week @ 2025-01-14 1057271/week @ 2025-01-21 1106260/week @ 2025-01-28 1168600/week @ 2025-02-04 1220726/week @ 2025-02-11 4873/week @ 2025-02-18

3,679,395 downloads per month
Used in 21,437 crates (949 directly)

MIT/Apache

2.5MB
43K SLoC

wasm-bindgen-futures

API Documentation

This crate bridges the gap between a Rust Future and a JavaScript Promise. It provides two conversions:

  1. From a JavaScript Promise into a Rust Future.
  2. From a Rust Future into a JavaScript Promise.

Additionally under the feature flag futures-core-03-stream there is experimental support for AsyncIterator to Stream conversion.

See the API documentation for more info.


lib.rs:

Converting between JavaScript Promises to Rust Futures.

This crate provides a bridge for working with JavaScript Promise types as a Rust Future, and similarly contains utilities to turn a rust Future into a JavaScript Promise. This can be useful when working with asynchronous or otherwise blocking work in Rust (wasm), and provides the ability to interoperate with JavaScript events and JavaScript I/O primitives.

There are three main interfaces in this crate currently:

  1. JsFuture

    A type that is constructed with a Promise and can then be used as a Future<Output = Result<JsValue, JsValue>>. This Rust future will resolve or reject with the value coming out of the Promise.

  2. future_to_promise

    Converts a Rust Future<Output = Result<JsValue, JsValue>> into a JavaScript Promise. The future's result will translate to either a resolved or rejected Promise in JavaScript.

  3. spawn_local

    Spawns a Future<Output = ()> on the current thread. This is the best way to run a Future in Rust without sending it to JavaScript.

These three items should provide enough of a bridge to interoperate the two systems and make sure that Rust/JavaScript can work together with asynchronous and I/O work.

Dependencies

~0.6–1.2MB
~24K SLoC