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

#104 in Asynchronous

Download history 909667/week @ 2024-12-01 1011051/week @ 2024-12-08 919845/week @ 2024-12-15 408356/week @ 2024-12-22 532415/week @ 2024-12-29 980971/week @ 2025-01-05 1216490/week @ 2025-01-12 1038494/week @ 2025-01-19 1089056/week @ 2025-01-26 1161002/week @ 2025-02-02 1272643/week @ 2025-02-09 1142874/week @ 2025-02-16 1255454/week @ 2025-02-23 1564248/week @ 2025-03-02 1548671/week @ 2025-03-09 1674212/week @ 2025-03-16

6,127,548 downloads per month
Used in 21,828 crates (969 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.2MB
~24K SLoC