82 releases

new 0.4.47 Nov 30, 2024
0.4.45 Oct 10, 2024
0.4.42 Mar 4, 2024
0.4.39 Nov 27, 2023
0.3.5 Nov 12, 2018

#80 in Asynchronous

Download history 881580/week @ 2024-08-14 900072/week @ 2024-08-21 820148/week @ 2024-08-28 914555/week @ 2024-09-04 858213/week @ 2024-09-11 839570/week @ 2024-09-18 904472/week @ 2024-09-25 911236/week @ 2024-10-02 939954/week @ 2024-10-09 975699/week @ 2024-10-16 969163/week @ 2024-10-23 930201/week @ 2024-10-30 909265/week @ 2024-11-06 930991/week @ 2024-11-13 892357/week @ 2024-11-20 613996/week @ 2024-11-27

3,524,587 downloads per month
Used in 19,400 crates (864 directly)

MIT/Apache

2.5MB
44K 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.3MB
~25K SLoC