Switch SSR examples from wasm-logger to tracing-web

[Copilot]

The two SSR examples (simple_ssr, ssr_router) used wasm-logger/log for browser-side logging. These are migrated to tracing-web + tracing-subscriber, consistent with the pattern established in yew-trunk-minimal-template.

Changes

• Cargo.toml (workspace): Add tracing-web = "0.1" and tracing-subscriber = { version = "0.3", features = ["fmt"] } as workspace dependencies.
• examples/simple_ssr/Cargo.toml / examples/ssr_router/Cargo.toml: Replace wasm-logger (and log) with tracing-web + tracing-subscriber in [target.'cfg(target_arch = "wasm32")'.dependencies].
• *_hydrate.rs binaries: Replace wasm_logger::init(...) with a tracing-subscriber registry backed by MakeWebConsoleWriter.

#[cfg(target_arch = "wasm32")]
{
    let fmt_layer = tracing_subscriber::fmt::layer()
        .with_ansi(false) // Only partially supported across browsers
        .without_time()   // std::time is not available in browsers
        .with_writer(tracing_web::MakeWebConsoleWriter::new());
    use tracing_subscriber::prelude::*;
    tracing_subscriber::registry().with(fmt_layer).init();
}

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[WorldSEnder]

There are other examples that use wasm_logger at the moment which could switch as well. Further, this does currently not configure a the same logging level as previously, which should be easy enough to fix with tracing_subscriber's API.

[Madoshakalaka]

There are other examples that use wasm_logger at the moment which could switch as well.

I specifically only did it to SSR examples, because tracing-web actually benefits there by collecting on the server side too.

our docs does mention all options so mayybe there is not enough motivation in switching all exampes?

Actually, now that I looked at the source, wasm-logger hasn't been having new commits for 6 years. Maybe that's enough motivation to adjust the docs and switch to tracing-web workspace-wide. That will belong to a different PR though.

this does currently not configure a the same logging level as previously, which should be easy enough to fix with tracing_subscriber's API.

will fix.

[Madoshakalaka]

@copilot fix.

[Copilot]

@copilot fix.

Added .with_filter(tracing_subscriber::filter::LevelFilter::TRACE) to the fmt layer in both hydrate binaries, matching the previous log::Level::Trace behavior. Commit: 0cb60a8

[Madoshakalaka]

looks good. I'm not sure if we should add .with_timer(UtcTime::rfc_3339()) to the examples. Opinions? @WorldSEnder

[WorldSEnder]

looks good. I'm not sure if we should add .with_timer(UtcTime::rfc_3339()) to the examples. Opinions?

I recommend against it in the tracing-web docs, besides missing (sys) support from std, all browsers have an option to show a timestamp next to the logged message in the debug console anyway.

[Madoshakalaka]

all browsers have an option to show a timestamp next to the logged message in the debug console anyway.

TIL

worked amazing

life saver, thanks