80 releases

0.4.45 Oct 10, 2024
0.4.43 Aug 12, 2024
0.4.42 Mar 4, 2024
0.4.39 Nov 27, 2023
0.3.5 Nov 12, 2018

#86 in Asynchronous

Download history 793542/week @ 2024-08-02 896935/week @ 2024-08-09 903875/week @ 2024-08-16 887991/week @ 2024-08-23 829251/week @ 2024-08-30 888269/week @ 2024-09-06 815147/week @ 2024-09-13 911529/week @ 2024-09-20 890637/week @ 2024-09-27 946952/week @ 2024-10-04 943058/week @ 2024-10-11 965621/week @ 2024-10-18 966481/week @ 2024-10-25 918316/week @ 2024-11-01 916880/week @ 2024-11-08 911518/week @ 2024-11-15

3,894,373 downloads per month
Used in 19,179 crates (859 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.5–1.2MB
~23K SLoC