rust-search-extension VS book

Rust Search Extension adds a section on docs.rs menubar which lists the features of a crate in a nice and easy to access format.

How do I use it? https://rust.extension.sh/ says "You can press space after the keyword", but what's the keyword? Like, after installing it, what's the key(s) I have to press to use it in the address bar?

Rust search extension helps you quickly navigate documentation between multiple crates.

Firefox users, see https://github.com/huhu/rust-search-extension/issues/190, with the patch applied I gather this means we just need another release to stop being warned about the increase in permissions.

Here is the explanation https://github.com/huhu/rust-search-extension/issues/190

there's also an extension for browsers ("Rust Search Extension")

If you have the Rust search browser extension installed, you'll have a tab labeled "Features" on docs.rs

Like many Rust features, there is a Rust/WASM tutorial and book that was very good. I was able to follow the tutorial to get up and running with development pretty easily... though this entire ecosystem kind of has way too many moving parts. Webpack? NPM? Nodejs? Just for this? It's a bit heavyweight, but I guess like 90% of the development in the world uses stuff like this now, huh?

For more information, you can refer to the Rust and WebAssembly.

As a starting point for Rust in general, you should read the book. And if you got some grasp of Rust, you should take a look at the book about Rust and Wasm.

I am following the Rust Wasm book. I have the following struct.

https://rustwasm.github.io/docs/book goes over how to compile to WASM and rendering to a canvas.

Rust 🦀 and WebAssembly 🕸 (英語)

I'm a little confused about how Rust fits into your UI-for-a-Python-API thing. Web UIs are typically written in Javascript or something that compiles to Javascript. Compiling Rust to Javascript is a not a common use of Rust at this time. The typical use of Rust in a web application would be the part that runs on the server (the "backend"), not the part that runs in the web browser (the "UI"). While you can write web UIs in Rust, this is a thing better learned after learning the normal way to do it, in Javascript.

AFAIK unwinding in WASM is not a thing: https://github.com/rustwasm/book/issues/76