Question 1

What is DepFixer?

Accepted Answer

DepFixer is a smart dependency analysis tool for JavaScript and TypeScript projects. It detects dependency conflicts, peer dependency mismatches, deprecated packages, and provides framework-aware migration recommendations by analyzing your package.json against 5M+ real compatibility records.

Question 2

How is DepFixer different from npm audit?

Accepted Answer

npm audit only checks for known security vulnerabilities. DepFixer goes much further — it detects peer dependency conflicts, version incompatibilities, framework-specific issues, and provides migration paths. For example, npm audit won't tell you that your version of @angular/material is incompatible with Angular 18, but DepFixer will.

Question 3

How is DepFixer different from depcheck?

Accepted Answer

depcheck finds unused dependencies and missing dependencies in your code. DepFixer focuses on compatibility — it finds version conflicts, peer dependency mismatches, and provides upgrade paths. They solve different problems and can be used together.

Question 4

What frameworks does DepFixer support?

Accepted Answer

DepFixer supports React (16-19), Angular (12-19), Vue (2-3), Next.js, NestJS, and Node.js. Framework-aware analysis understands specific requirements like TypeScript version compatibility, RxJS versions for Angular, and peer dependency requirements.

Question 5

Is DepFixer free?

Accepted Answer

DepFixer offers a free audit tier that shows a summary of your dependency health. Full analysis with detailed conflict reports, migration recommendations, and fix generation requires credits starting at $4.99.

Question 6

How does DepFixer detect conflicts?

Accepted Answer

DepFixer analyzes your package.json against a database of 5M+ real compatibility records from the npm registry. It checks peer dependency requirements, framework-specific version constraints, cross-package compatibility rules, and known breaking changes. This is real data, not AI guesses.

Question 7

What is a peer dependency conflict?

Accepted Answer

A peer dependency conflict occurs when a package requires a specific version of another package (its 'peer'), but your project has an incompatible version installed. For example, if @angular/material@16 requires @angular/core@16 but you have @angular/core@18, that's a peer dependency conflict. DepFixer detects these automatically.

Question 8

What does the health score mean?

Accepted Answer

The health score (0-100) rates your project's dependency health based on the number and severity of conflicts found. A score above 90 means your dependencies are well-maintained. Below 70 means there are significant issues that should be addressed.

Question 9

Can DepFixer fix my dependencies automatically?

Accepted Answer

Yes. After analysis, DepFixer can generate a corrected package.json with all conflicts resolved. You can review the changes before applying them. The CLI command `depfixer fix` applies fixes automatically.

Question 10

How does migration analysis work?

Accepted Answer

When you select a target framework version (e.g., Angular 18), DepFixer projects all your dependencies to their compatible versions. It maps every package to the correct version that works with your target framework, identifies breaking changes, and provides a step-by-step migration plan.

Question 11

What Angular versions can I migrate between?

Accepted Answer

DepFixer supports Angular migrations from version 12 through 19. It handles core packages (@angular/core, @angular/cli), ecosystem packages (@angular/material, @ngrx/store), and TypeScript version requirements for each Angular version.

Question 12

What React versions can I upgrade between?

Accepted Answer

DepFixer supports React upgrades from version 16 through 19, including the React 17→18 migration (concurrent features, new root API) and React 18→19 migration (React Compiler, Actions). It handles react-dom, react-router, Redux, MUI, and other ecosystem packages.

Question 13

How do I install the DepFixer CLI?

Accepted Answer

Install globally with `npm install -g depfixer` or run directly with `npx depfixer analyze`. The CLI works with Node.js 18 or higher on Windows, macOS, and Linux.

Question 14

Can I use DepFixer in CI/CD pipelines?

Accepted Answer

Yes. DepFixer supports CI mode with non-interactive output and exit codes. Use `depfixer analyze --ci` to integrate into GitHub Actions, GitLab CI, Jenkins, or any CI/CD pipeline. It returns non-zero exit codes when conflicts are found.

Question 15

Do I need to share my source code?

Accepted Answer

No. DepFixer only reads your package.json file — your source code never leaves your machine. The CLI sends only the dependency list to the analysis API, not your code.

Frequently Asked Questions

General

How It Works

Migration

CLI & Integration

Ready to Fix Your Dependencies?