Ben Frankel

> I'd like to see the wasm-opt part also go somewhere more discoverable, but that's for a follow-up Yeah, it's just that I would've had to get into `wasm-bindgen-cli` first...

Yeah this seems like a bug. At the very least it's surprising behavior. `cargo binstall --git=https://github.com/foo/bar quux` can't find an appropriate release, so as a fallback it runs `cargo install...

> Mostly our api uses `X::foo() -> T` panics and `X::get_foo() -> Option` is non-panicing. This is also how the standard library tends to be set up. This isn't true...

My take on how this (and the related issues) should be fixed for bevy 0.15: https://github.com/bevyengine/bevy/issues/13968#issuecomment-2185259558

Oh. I just realized that `.add_after` takes two generics, so you have to write it out as `.add_after::(...)`. It doesn't have to be this way: if `.add_after` used one generic...

A caveat I ran into: If you do `DefaultPlugins.replace::(MyFooPLugin)`, it will panic if `FooPlugin` does not exist in `DefaultPlugins` because you disabled its feature. And if you're replacing a plugin...

Maybe the word "extensible" to highlight the flexibility / modularity that comes from user code being similar to engine code.

Hit this with UI image during the game jam :) As a workaround, I made a child node of the UI image with 100% width and height and put the...

Note that this also opens the door to expanding the type into an enum as such (from `pyri_state`): ```rust pub enum DespawnOnExit { Single, #[default] Recursive, Descendants, #[doc(hidden)] _PhantomData(PhantomData), }...