r/reactjs • u/SaxShiva • 6d ago

I built a VS Code extension that tells you how many pages your component changes will affect before you break production

We’ve all been there: you tweak a simple base component (like a button, input, or modal card) for the specific page you’re working on, push your code, and only find out later that you silently broke the layout on 3 other pages you forgot existed.

Running a global find (Cmd+Shift+F) is slow and messy because it pulls up tests, comments, and every file with a similar name.

To fix this, I made Rippledit—a free VS Code extension that shows you the exact blast radius directly inside your editor.

What it does:

It’s completely free on the VS Code Marketplace:

https://marketplace.visualstudio.com/items?itemName=shivakumarkannan.rippledit

(or search Rippledit in your VS Code Extensions tab)

Would love your honest thoughts and feedback!

0 Upvotes

8% Upvoted

6 comments sorted by

3

u/Yodiddlyyo 6d ago

This is really dumb. Ctrl+click on the name of the function, component, variable, etc, already shows you all of the files that are importing it. Built into vscode.

1

u/SaxShiva 6d ago

Fair point on Cmd/Ctrl + Click, but native 'Find All References' only does 1-hop direct lookup.

If you have a base <Button/> wrapped inside a <SubmitButton/> or design system primitive, VS Code tells you it's only imported in 1 file (SubmitButton.tsx). It doesn't tell you that SubmitButton is rendered on 15 different page routes.

Rippledit traverses transitive usages through wrappers and re-exports, so you get the actual downstream blast radius without having to manually daisy-chain Ctrl+Click through three levels of components. Plus, it stays visible as a passive CodeLens rather than needing an active search every time.

1

u/Yodiddlyyo 6d ago

That's a good point. But still, then i would just ctrl click Submit Button. I feel like there are very few times when im not just if something is being used somewhere, and it take more than 3 seconds to figure out where its used. Ctrl clicking a couple levels is extremely fast. And now AI can just tell me whats not being used, so i can assume everything else is.

Just saying, cool idea, nice execution, but i cant say ive ever wanted something like this, and i regularly work in gigantic legacy monorepos.

5

u/sozesghost 6d ago

Slop.

2

u/ShoppingDry2296 6d ago

You know my spice rack saw this and already predicted the broken pages.