henrik
henrik
I'm not sure what you want to achieve with: `#![rustversion::attr(nightly, feature(unboxed_closures))]` Use nightly, but only if feature *unboxed_closures* is not available on stable? Wouldn't simply `#[rustversion::nightly]` suffice? When the feature...
Actually, shouldn't it be: `#[rustversion::attr(nightly, feature(unboxed_closures))]`, without the exclamation mark?
How about using [rustc_version](https://crates.io/crates/rustc_version) for automatically setting the `stable` feature? I did a test and it seems to work well. I can do a PR, but probably best to wait...
Ok, so I finally rebased it on main. There is now only one version defined for the libs: the one specified in the root workspace Cargo.toml file. If this is...
> Mostly because if cargo-leptos is not used, then I need it to work with wasm-pack without any env vars set. There is the possibility to assume that `cargo-leptos` is...
@abishekatp If you need any [cargo-leptos](https://github.com/akesson/cargo-leptos) integration or changes then feel free to contact me. I'm quite busy so I can only promise to reply to questions and help with...
You mentioned `async` rendering. A use-case would be when a Leptos server would fully render a page (pre-load data) when an SEO bot requests it and otherwise use the data...
Regarding the mutually exclusive features: I promise that if you ever hear from me again about that, then it will be with a concrete proposal. Unfortunately, I don't have time...