Thaw/v0.5

[lizidev]

This is meant to prepare for a 0.5.0-alpha release.

It will include the following breaking changes:

• Update leptos to v0.8.0-alpha.
• RatingColor adds Marigold attribute.
• InputType adds Number prop.
• The icon prop of Icon is changed to icondata_core::Icon type.
• The value prop of MenuItem is changed to generic type.

---

• Theme is changed to use getset.

Reason: When adding new components requires changing ColorTheme, it is very easy to make breaking changes.

example:

// 0.4
let _ = theme.common.font_weight_bold;
let _ = theme.color.color_brand_background;
theme.common.font_weight_bold = "700".to_string();
theme.color.color_brand_background = "#f5222d".to_string();

// 0.5
let _ = theme.common.font_weight_bold();
let _ = theme.color.color_brand_background();
theme.common.set_font_weight_bold("700".to_string());
theme.color.set_color_brand_background("#f5222d".to_string());

[povilasb]

Hey, any plans on proceeding with this PR?

[lizidev]

@povilasb I plan to finish working on https://github.com/thaw-ui/thaw/milestone/4 first, and then release v0.5.

[povilasb]

Perfect.

Heads up that I've been testing this branch with leptos = 0.8.2 and it produces a cryptic compilation error when server function is declared:

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.11s
�[38;5;77m       Cargo�[0m finished �[38;5;241mcargo build --package=thaw-demo --lib --target-dir=/Users/povilas/projects/thaw-demo/target/front --target=wasm32-unknown-unknown --no-default-features --features=hydrate�[0m
�[38;5;77m       Front�[0m generating JS/WASM with wasm-bindgen
�[31mThe application panicked (crashed).�[0m
Message:  �[36mthaw_demo::app::_::__ctor::h0c98ab51124d5ea9: Read a negative address value from the stack. Did we run out of memory?�[0m
Location: �[35m/Users/povilas/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wasm-bindgen-wasm-interpreter-0.2.100/src/lib.rs�[0m:�[35m245

• Full error message here.

• You can checkout a reproducible example at: https://github.com/povilasb/thaw-demo/
  Checkout the history how to reproduce it: https://github.com/povilasb/thaw-demo/

• The server function works, but as soon as I add thaw dependency it starts crashing: povilasb/thaw-demo@28be2d7

• Removing the server function declaration, make the app build again.

$ rustc --version
rustc 1.88.0 (6b00bc388 2025-06-23)

$ cargo leptos --version
cargo-leptos 0.2.36

$ sw_vers
ProductName:            macOS
ProductVersion:         15.5
BuildVersion:           24F74

Let me know if you need more info.

[lizidev]

@povilasb The Thaw feature should not be enabled by default.

[povilasb]

That worked indeed. Thank you 🙇

I still am a little confused on when to use the SSR feature?
I figured I should be using it when I'm building an SSR app 🤔 based on the docs

To enable the ssr mode, the following configurations are required:

thaw = { ..., features = ["ssr"] }

[povilasb]

Heads up that there will be a few reactive-graph related issues with leptos 0.8.5:

error[E0277]: the trait bound `S: reactive_graph::owner::storage::Storage<ArcField<Vec<T>>>` is not satisfied
   --> /Users/povilas/projects/thaw/thaw_utils/src/signals/model/vec_model.rs:261:48
    |
261 |         let field: Field<Vec<T>, S> = subfield.into();
    |                                                ^^^^ the trait `reactive_graph::owner::storage::Storage<ArcField<Vec<T>>>` is not implemented for `S`
    |
    = note: required for `Field<Vec<T>, S>` to implement `From<Subfield<Inner, Prev, Vec<T>>>`
    = note: required for `Subfield<Inner, Prev, Vec<T>>` to implement `Into<Field<Vec<T>, S>>`
help: consider further restricting type parameter `S` with trait `Storage`
    |
255 |     S: Storage<T> + Storage<ArcField<Vec<T>>> + Storage<Option<T>> + Storage<Vec<T>> + reactive_graph::owner::storage::Storage<reactive_stores::ArcField<std::vec::Vec<T>>>,
    |                                                                                      ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

[lizidev]

@povilasb

I still am a little confused on when to use the SSR feature?
I figured I should be using it when I'm building an SSR app 🤔 based on the docs

The documentation is a bit misleading here, I will correct this later.

Specifically, we should not activate the corresponding features, but only provide two features to the cargo-leptos tool, which will build two packages based on these two features.

cargo build --features=hydrate
cargo build --features=ssr

Heads up that there will be a few reactive-graph related issues with leptos 0.8.5:

There are no problems in my local and CI. Can you provide the execution command and version information (execute cargo -vV command)?

[adamnemecek]

Commendable effort! When do you think this might be merged?

[povilasb]

@lizidev just tested with the latest version of this branch - compiles fine now.
Thank you 🙇

[lizidev]

Since leptos v0.8 has been out for a while, and to better facilitate CI/CD, I'm merging the thaw/v0.5 branch into main.

For issues related to thaw-v0.4, please check out the thaw-v0.4 branch.