React tooling lacks true dependency graphs, leaving developers guessing what breaks

A developer essay argues that most React tooling relies on text search and file lists rather than a true dependency graph, making it difficult to assess the real impact of deleting or changing a file. The piece distinguishes between the component tree, which shows runtime parent-child rendering relationships, and the dependency graph, which maps compile-time import relationships across files and packages. Building an accurate dependency graph is complicated by real-world factors such as barrel file chains, path aliases, dynamic imports, type-only edges, and circular dependencies. The author outlines several practical queries a proper dependency graph should support, including resolving imports through barrels, tracing inbound references, checking reachability from an entry point, and identifying chokepoint files. The argument is that turning these capabilities into queryable tools would give developers an objective basis for refactoring decisions rather than relying on intuition.