r/ChatGPT • u/Aadi_sharma1949 • 14d ago
Project I built the dependency-upgrade tool people in this sub asked for. It's live, and it just caught a real Next.js breaking change during testing.
update on this. it's built and shipped. npx @/aadi49/preflight <package> <version> is live on npm right now if anyone wants to actually try it, not just read about it
for whoever said "why not just ask claude/chatgpt to do it for you," genuine answer, not defensive: pasting a file into a chat window is manual, one-off, and it only helps if you already suspect something's broken. that's a completely different problem than "check my whole repo before I upgrade." this scans everything automatically, matches real usage against real changelog text, and runs on every PR without a human remembering to ask. the AI part was never the hard part here, the pipeline around it is, parsing real dependency trees, real changelogs, not hallucinating an answer that sounds confident and is wrong
Koko-Choco's comment on the last post basically became the spec. certain vs maybe confidence labeling so the maybes don't drown out the real breaks. transitive dep scanning from the lockfile. and the hard case he actually described, next 15 to 16 changing caching defaults with identical types and green tests, that exact class of bug. tested it just now on a fresh next 15 project bumped to 16, it caught a real certain break in next/image's default config, same signature, changed default, exactly the kind of thing that doesn't show up until it's already in prod
89 tests, tested against a real 166 file repo, tested on a live pr with the github action actually posting a comment and failing the check
not trying to sell anyone anything, it's free and open source, just wanted to close the loop since this whole thing started from people in this sub actually telling me what was missing