Crates.io | web-sys |
lib.rs | web-sys |
version | 0.3.72 |
source | src |
created_at | 2018-07-19 19:42:48.824097 |
updated_at | 2024-10-10 22:14:51.650211 |
description | Bindings for all Web APIs, a procedurally generated crate from WebIDL |
homepage | https://rustwasm.github.io/wasm-bindgen/web-sys/index.html |
repository | https://github.com/rustwasm/wasm-bindgen/tree/master/crates/web-sys |
max_upload_size | |
id | 75113 |
size | 10,468,109 |
web-sys
Raw bindings to Web APIs for projects using wasm-bindgen
.
This crate by default contains very little when compiled as almost all of its
exposed APIs are gated by Cargo features. The exhaustive list of features can be
found in crates/web-sys/Cargo.toml
, but the rule of thumb for web-sys
is
that each type has its own cargo feature (named after the type). Using an API
requires enabling the features for all types used in the API, and APIs should
mention in the documentation what features they require.
If you don't see a particular web API in web-sys
, here is how to add it.
webidls/unstable
folder. You can often find the IDL by going to the MDN
docs page for the API, scrolling to the bottom, clicking the
"Specifications" link, and scrolling to the bottom of the specification
page. For example, the bottom of the MDN
docs on the
MediaSession API takes you to the
spec. The
very bottom of that page
is the IDL.[Throws]
cargo run --release --package wasm-bindgen-webidl -- webidls src/features ./Cargo.toml
git add .
to add all the generated files into git....
## Unreleased
### Added
...
* Added <your addition>
[#1234](https://github.com/rustwasm/wasm-bindgen/pull/1234) # <- link to your PR