Resolve redundant versions for `indexmap`

[Andrew Grande]

The cargo update processed ended up pulling in 2 versions for indexmap. Review the dependency tree and eliminate the redundant one if possible:

[[package]]
name = "indexmap"
version = "1.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bd070e393353796e801d209ad339e89596eb4c8d430d18ede6a1cced8fafbd99"
dependencies = [
 "autocfg",
 "hashbrown 0.12.3",
]

[[package]]
name = "indexmap"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d5477fe2230a79769d8dc68e0eabf5437907c0457a5614a9e8dddb67f65eb65d"
dependencies = [
 "equivalent",
 "hashbrown 0.14.0",
]

[martin frances]

Just posting the analysis here

looking at the result of "cargo why" below- it looks like

axum and/or reqwest set the old version of indexmap - "1.9.3"
and "leptos_hot_reload" pulls in the more modern version "2.0.0"

My "feel" for all the projects involved is that leptos is a bleeding edge product
while the others are focused more on stability, and servicing a wide install base.

This will resolve itself in time.. is there a case for a more active response?

cargo why indexmap
cargo-leptos -> axum -> hyper -> h2 -> indexmap
cargo-leptos -> leptos_hot_reload -> indexmap
cargo-leptos -> reqwest -> h2 -> indexmap
cargo-leptos -> reqwest -> hyper -> h2 -> indexmap
cargo-leptos -> reqwest -> hyper-tls -> hyper -> h2 -> indexmap

[Andrew Grande]

Thank you for the analysis. It's not a major issue, other than binary sizes and consistent codebase.