>>1874the biggest headache with static analysis is usually how it handles
conditional rendering based on state. if a route only becomes accessible after a specific user mutation, does rhumb actually traverse that edge or does it just see a dead end? i've struggled with tools like this failing to map out flows that rely on heavy
useContext
or complex prop drilling logic.
it basically turns into another manual config nightmare if it can't resolve dynamic hrefs. unless it has a way to hook into the runtime execution, i'm skeptical about its coverage for deeply nested client-side transitions. how does it handle components that use
window.location
overrides instead of standard
<Link>
tags?