u/Melodic-Funny-9560

Hey everyone,

I’ve been working on something called Devlens — a tool to visualize React / Next.js codebases as an interactive graph.

Built this mainly because PR reviews and onboarding were getting annoying…

had to jump across a bunch of files just to understand how things connect and what might break.

With this, you can open a route or component and:

see dependencies both ways

understand how a feature is structured

check the blast radius before changing something

Also added summaries + basic security analysis so you get context quickly.

There’s a short demo video below that explains it better.

https://youtu.be/6OMsk8lNv4c

Still early — would love some honest feedback.

https://github.com/devlensio/devlensOSS

https://Devlens.io

Hey everyone,

I’ve been working on something called Devlens — a tool to visualize React / Next.js codebases as an interactive graph.

Built this mainly because PR reviews and onboarding were getting annoying…

had to jump across a bunch of files just to understand how things connect and what might break.

With this, you can open a route or component and:

see dependencies both ways

understand how a feature is structured

check the blast radius before changing something

Also added summaries + basic security analysis so you get context quickly.

There’s a short demo below that explains it better.

Still early, though the open source version is out I am still working on the cloud version which will have many more features. would love some honest feedback.

GitHub : https://github.com/devlensio/devlensOSS

I kept running into this problem while working on larger codebases:

I’d make a small change in one file… and somehow break something completely unrelated.

It’s surprisingly hard to answer:

“what else does this piece of code affect?”

So I built an open source tool called Devlens.

It analyzes a codebase and builds a dependency graph, so when you select a file, it shows all the other parts that might be impacted (kind of like a “blast radius” for code changes).

Right now it:

\- works for javascript, Reactjs, nodejs, nextjs

\- can generate summaries for each node efficiently explaining what a node does and how

\- Security analysis of your codebase

\- maps dependencies between functions and different types components

\- highlights impacted areas when you select something

\- helps navigate unfamiliar codebases a bit faster

Would love to know:

\- does this feel like a real problem to you?

\- how do you usually figure out impact before making changes?

Project:

https://github.com/devlensio/devlensOSS

Website:

https://devlens.io

Demo:

https://youtu.be/6OMsk8lNv4c