While working with larger React / Next.js codebases, I noticed a lot of PR review time goes into understanding the impact of a change rather than the change itself.
Things like:
what depends on this? what else could this affect? how far does this propagate?
usually require a lot of manual tracing across files and components.
So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.
Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.
1 comment
[ 2.9 ms ] story [ 9.6 ms ] threadwhat depends on this? what else could this affect? how far does this propagate?
usually require a lot of manual tracing across files and components.
So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.
Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.
Website: https://devlens.io GitHub: https://github.com/devlensio/devlensOSS