The following seem to form a cycle or will in the future
- ahash 0.6 depends on getrandom
- getrandom 0.2 optionally depends on wasm-bindgen
- wasm-bindgen 0.2.69 optionally depends on serde_json
- serde_json optionally depends on indexmap
- indexmap depends on hashbrown 0.9
- hashbrown in git depends on ahash 0.6.
It is unlikely to happen in practice but can cargo handle the case where all the optional features are enabled?