# `iced_web` [![Documentation](https://docs.rs/iced_web/badge.svg)][documentation] [![Crates.io](https://img.shields.io/crates/v/iced_web.svg)](https://crates.io/crates/iced_web) [![License](https://img.shields.io/crates/l/iced_web.svg)](https://github.com/hecrj/iced/blob/master/LICENSE) [![project chat](https://img.shields.io/badge/chat-on_zulip-brightgreen.svg)](https://iced.zulipchat.com) `iced_web` takes [`iced_core`] and builds a WebAssembly runtime on top. It achieves this by introducing a `Widget` trait that can be used to produce VDOM nodes. The crate is currently a __very experimental__, simple abstraction layer over [`dodrio`]. ![iced_core](../docs/graphs/web.png) [documentation]: https://docs.rs/iced_web [`iced_core`]: ../core [`dodrio`]: https://github.com/fitzgen/dodrio ## Installation Add `iced_web` as a dependency in your `Cargo.toml`: ```toml iced_web = "0.1.0-alpha" ``` __Iced moves fast and the `master` branch can contain breaking changes!__ If you want to learn about a specific release, check out [the release list]. [the release list]: https://github.com/hecrj/iced/releases ## Usage The current build process is a bit involved, as [`wasm-pack`] does not currently [support building binary crates](https://github.com/rustwasm/wasm-pack/issues/734). Therefore, we instead build using the `wasm32-unknown-unknown` target and use the [`wasm-bindgen`] CLI to generate appropriate bindings. For instance, let's say we want to build the [`tour` example]: ``` cd examples cargo build --example tour --target wasm32-unknown-unknown wasm-bindgen ../target/wasm32-unknown-unknown/debug/examples/tour.wasm --out-dir tour --web ``` Then, we need to create an `.html` file to load our application: ```html Tour - Iced ``` Finally, we serve it using an HTTP server and access it with our browser. [`wasm-pack`]: https://github.com/rustwasm/wasm-pack [`wasm-bindgen`]: https://github.com/rustwasm/wasm-bindgen [`tour` example]: ../examples/README.md#tour