38 releases
0.2.100 | Jan 12, 2025 |
---|---|
0.2.99 | Dec 7, 2024 |
0.2.97 | Nov 30, 2024 |
0.2.92 | Mar 4, 2024 |
0.2.67 | Jul 28, 2020 |
#1655 in WebAssembly
152,566 downloads per month
Used in 34 crates
(via wasm-bindgen-cli-support)
46KB
803 lines
wasm-bindgen
Facilitating high-level interactions between Wasm modules and JavaScript.
Guide (main branch) | API Docs | Contributing | Chat
Built with 🦀🕸 by The Rust and WebAssembly Working Group
Install wasm-bindgen-cli
You can install it using cargo install
:
cargo install wasm-bindgen-cli
Or, you can download it from the release page.
If you have cargo-binstall
installed,
then you can install the pre-built artifacts by running:
cargo binstall wasm-bindgen-cli
Example
Import JavaScript things into Rust and export Rust things to JavaScript.
use wasm_bindgen::prelude::*;
// Import the `window.alert` function from the Web.
#[wasm_bindgen]
extern "C" {
fn alert(s: &str);
}
// Export a `greet` function from Rust to JavaScript, that alerts a
// hello message.
#[wasm_bindgen]
pub fn greet(name: &str) {
alert(&format!("Hello, {}!", name));
}
Use exported Rust things from JavaScript with ECMAScript modules!
import { greet } from "./hello_world";
greet("World!");
Features
-
Lightweight. Only pay for what you use.
wasm-bindgen
only generates bindings and glue for the JavaScript imports you actually use and Rust functionality that you export. For example, importing and using thedocument.querySelector
method doesn't causeNode.prototype.appendChild
orwindow.alert
to be included in the bindings as well. -
ECMAScript modules. Just import WebAssembly modules the same way you would import JavaScript modules. Future compatible with WebAssembly modules and ECMAScript modules integration.
-
Designed with the "Web IDL bindings" proposal in mind. Eventually, there won't be any JavaScript shims between Rust-generated wasm functions and native DOM methods. Because the Wasm functions are statically type checked, some of those native methods' dynamic type checks should become unnecessary, promising to unlock even-faster-than-JavaScript DOM access.
Guide
📚 Read the wasm-bindgen
guide here! 📚
You can find general documentation about using Rust and WebAssembly together here.
API Docs
MSRV Policy
Libraries that are released on crates.io have a MSRV of v1.57. Changes to the MSRV will be accompanied by a minor version bump.
CLI tools and their corresponding support libraries have a MSRV of v1.76. Changes to the MSRV will be accompanied by a patch version bump.
License
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
See the "Contributing" section of the guide for information on
hacking on wasm-bindgen
!
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
lib.rs
:
Transformation for wasm-bindgen to enable usage of externref
in a wasm
module.
This crate is in charge of enabling code using wasm-bindgen
to use the
externref
type inside of the Wasm module. This transformation pass primarily
wraps exports and imports in shims which use externref
, but quickly turn them
into i32
value types. This is all largely a stopgap until Rust has
first-class support for the externref
type, but that's thought to be in the
far future and will take quite some time to implement. In the meantime, we
have this!
The pass here works by collecting information during binding generation
about imports and exports. Afterwards this pass runs in one go against a
Wasm module, updating exports, imports, calls to these functions, etc. The
goal at least is to have valid Wasm modules coming in that don't use
externref
and valid Wasm modules going out which use externref
at the fringes.
Dependencies
~5.5MB
~116K SLoC