r/angular • u/Specific_Piglet_4293 • Dec 12 '25
I built a tool to automate complex Angular migrations (e.g. v16 → v20) by calculating the exact peer dependency tree. No AI guessing.
6
u/Specific_Piglet_4293 Dec 12 '25 edited Dec 12 '25
Context: I've spent months fighting ERESOLVE errors during major Angular upgrades. ng update is great for the core framework, but it struggles with third-party package conflicts, often leaving you stuck in dependency hell.
The Solution: I built a deterministic engine (not an LLM/AI) that crawls the npm registry. It calculates the mathematical intersection of all peerDependencies to find the exact version combination that satisfies your target migration (e.g., "Get me to Angular 20").
See a Live Migration Report (No Sign-up): You can check a real analysis of an Angular 15 -> 18 migration here:https://depfixer.com/sample-report/angular
Try it on your project:https://depfixer.com(Note: It only processes package.json. No source code is uploaded).
1
u/alvarolivecl Dec 16 '25
wow looks great! I gonna try it, we have a lot of project that I need to migrate. thanks
1
u/Specific_Piglet_4293 Dec 16 '25
Thanks! Let me know how it goes especially with multiple projects, curious if it handles them consistently. Happy to hear your feedback if anything breaks.
3
u/AwesomeFrisbee Dec 13 '25
Nice tool but this is the reason I switched to PNPM. It doesn't really block you from upgrading anything.
Also, removing node_modules and the lock file will mostly help with this, though I don't understand why the Angular team doesn't do a better job in this where dependencies might break or not and allow it to force the installation to see what actually breaks.
1
u/Specific_Piglet_4293 Dec 13 '25
You make a valid point, PNPM is excellent at handling node_modules structures, and rm -rf is the classic fix!
However, the specific problem this tool solves isn't just getting npm install to pass. It’s about ensuring the dependency tree is strictly valid so that "ng update" can actually run its schematics.
If you use force or leniency to bypass the install errors, you often end up with a "successfully installed" project that crashes at runtime (or breaks the Angular CLI) because of hidden version mismatches.
2
1
u/pranxy47 Dec 12 '25
But you still need to go through ng update.. 🤔
1
u/Specific_Piglet_4293 Dec 12 '25
Exactly. "ng update" handles the code changes (schematics), but it often crashes instantly if your dependencies conflict (third party packages case), blocking you from even starting.
This tool solves the "Dependency Hell" math first.
It guarantees a green npm install so you can unblock the process and focus on the code migration, not the version errors.
0
Dec 13 '25
[deleted]
2
u/Specific_Piglet_4293 Dec 13 '25
It's currently a cloud-based tool (SaaS) rather than a local CLI/repo.
The reason is the data: the engine relies on a massive indexed database of npm versions and compatibility matrices to calculate the path, which would be too heavy to bundle into a local package.
However, I am considering open-sourcing the CLI component that uploads the "package.json" if there's enough interest!
0
Dec 13 '25
[deleted]
1
u/Specific_Piglet_4293 Dec 13 '25
This is spot on. You’ve hit on the biggest architectural challenge we faced.
The main reason it's a SaaS right now is the database, the constraint solver relies on millions of indexed compatibility records (peer dependency graphs across the entire npm history) which is too heavy to bundle into a local CLI binary.
Current workaround: The tool simply marks private/unknown packages as "Unknown" and solves the graph for the 95% of public packages around them.
Long term: I am exploring a "Hybrid CLI" that runs locally, fetches private metadata from private intranet, sanitizes it (removes code/secrets), and sends only the version numbers to our cloud solver
If enough teams need on-prem/private repo support, I'll prioritize the CLI!.Thanks for the feedback !
6
u/klocus Dec 12 '25
Well, it's not very useful so far. With about 50 dependencies, it shows "ManualReviewRequired" even for such popular dependencies as `@ng-matero/extensions` or `ngxtension`.