Ask HN: Would you use a "blast radius" view during PR reviews?
I’m building a tool around this idea and wanted to sanity check it.
In larger React / Next.js codebases, PR reviews often feel less about the change itself and more about understanding its impact.
I usually end up:
jumping across multiple files tracing dependencies manually trying to figure out what else might break
So I’ve been working on a way to visualize the codebase and show a “blast radius” for a component — basically what depends on it and what it affects.
I am genuinely trying to understand wether the tool I am building can be used in professional setup ?
Here is the open source version of the tool if anyone is interested.. https://github.com/devlensio/devlensOSS
here is the demo: https://youtu.be/6OMsk8lNv4c
No comments yet.