It is an open-source project and I will introduce soon its mcp/cli counterpart so that graphical context and sumaries can be given to LLMs/Agents directly through the mcp integration.

https://github.com/devlensio/devlensOSS https://devlens.io

Comments URL: https://news.ycombinator.com/item?id=48442536

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48176033

Points: 1

# Comments: 2

Having said that I really hope this model of deepseek, performs significantly on par with the claude saunnet model.

You can star the repo if you like the project. I am still working on cloud version which will have lots of features.

Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file/function where it will affect my Codebase which is specially useful for PR review.

The open source version is live at https://github.com/devlensio/devlensOSS

You can star the repo if you like the project. I am still working on cloud version which will have lots of features.

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.

Website: https://devlens.io GitHub: https://github.com/devlensio/devlensOSS

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.

Website: https://devlens.io GitHub: https://github.com/devlensio/devlensOSS

It visualizes React / Next.js codebases as an interactive graph so you can understand how features and components connect without manually tracing files.

Main focus right now is helping with:

PR reviews (understanding blast radius / impact of changes) onboarding to large codebases understanding unfamiliar parts of a system faster

Also experimenting with summaries + security analysis directly on components.

Still early, but it’s been pretty useful for me so far.

https://devlens.io https://github.com/devlensio/devlensOSS

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

Comments URL: https://news.ycombinator.com/item?id=48007920

Points: 2

# Comments: 0

Even when they had intel processors, they were efficient. Is it because of the OS, or the hardware?

Comments URL: https://news.ycombinator.com/item?id=47913071

Points: 3

# Comments: 2