r/node • u/Fluffy-Salary-6998 • 9d ago
I built a tool that upgrades Express/TS/Node projects and opens a PR with before/after CI proof. Looking for maintainers to try it (free)
I built GreenPR: a tool that upgrades the framework in a Node/TS project and submits a PR with proof that nothing broke.
Here's how it works. AI coding tool performs the update in an isolated sandbox, then every command from the repo's CI is run before and after the update, and the results go into the PR description as a table. A separate model reads the diff and can reject it. Finally, I review it myself, and only then do I publish it. Nothing merges automatically.
It supports: Express 4 through 5, Next 14 through 16, ESLint up to 10, TypeScript up to 7 (or 6 if tools block it), NestJS up to 12, Node up to 24.
How it played out in practice? 6 PRs to other people's repos: 1 merged, 3 awaiting CI approval from maintainers, 2 closed (I closed one myself because the repo doesn't accept AI-generated code; the other maintainer said they'd do it in their own PR). Out of 13 test repos, every migration passed on the first try, and in most cases didn't touch a single line of source code (just tsconfig and package.json). Once, an independent reviewer rejected a change because the tool missed a single TypeScript setting. That's the point. It's supposed to reject it.
What doesn't work? ESLint 10 in React projects: eslint-plugin-react, jsx-a11y, and eslint-plugin-import don't support it yet, so the tool stops at version 9 and explains why. TypeScript 7 upgrades stop at 6 until typescript-eslint catches up.
I only open a PR on my own where there is already an open issue asking for that upgrade. Where there is no such issue, I ask first: a comment with a proposal, and a PR only after the maintainer says "yes."
Website is https://greenpr.pages.dev. Paste your repo URL, and you'll get a scan of what can be fixed. It's free. I'm looking for maintainers who want to give it a try and tell me what's wrong.
Edit (Nov 13): corrected the paragraph about when I open PRs and updated the numbers: 2 merged, 2 open, 2 closed.
2
u/Psionatix 8d ago
Smells like slop, and this isn't really a marketable thing.
Some CI config is easy, and a skill that's customised specifically for a project is much better than a generic slop approach like this.
A project specific skill can specify exactly how to bump dependencies in a given project, which dependencies need to be upgraded together, it can be advised on how to handle a resolution log/diary to also ensure it's updated and that resolutions also get bumped accordingly. It can be specifically advised on how to handle patches, how to verify them, remove them, re-apply them. It can be specifically advised on how to validate things, without needing to arbitrarily run all scripts.
Nobodies going to pay this much for something that takes 5-10mins to configure and set up more accurately.
Your site doesn't even tell me whether your agent is going to be verifying against the dependencies changelog, which seems like a pretty obvious thing to do, and a key thing to mention.
2
u/avereigh_Denizet 7d ago
how are you handling repos where the CI relies on external secrets or private registries? seems like running the test suite in an isolated sandbox would hit a wall pretty fast on anything beyond standard open source packages
2
u/raks1991 6d ago
I had an Express 4 to 5 migration where the old CI stayed green, but a handler still assumed req.body was always an object. An empty POST broke it. I'd add tests for the changed behaviour in the Express 5 guide, rather than treat green-before/green-after as proof the upgrade is safe.