My general understanding of a "conflicting peer dependency" error is that some package I depend upon is expressing a peer dependency on a package version spec which does not match the version of that package that I actually have installed.įor example, if my project has direct dependencies on packages A and B, and I have version 12.0.0 of A installed but my version of B has a peer dependency on ^11.0.0 of package A, then I will get a conflicting peer dependency error, because I'm using B with a version of A that it is potentially incompatible with.
This can be reproduced by running npm install in the root of this Github branch (I'm using npm 7.10.0.) Npm ERR! to accept an incorrect (and potentially broken) dependency resolution. Npm ERR! this command with -force, or -legacy-peer-deps
Npm ERR! Fix the upstream dependency conflict, or retry Npm ERR! Conflicting peer dependency: ERR! ERR! peerOptional || ^11.2.0-next" from ERR! ERR! dev from the root project Npm ERR! Found: ERR! ERR! dev from the root project Npm ERR! ERESOLVE unable to resolve dependency tree Here's the error message I'm trying to interpret: npm ERR! code ERESOLVE I feel like if I understood that, I'd have a chance of figuring out how to solve the problem on my own. However, I've struggled to find information on what these errors actually mean. I see a lot of questions on this site asking for help fixing such errors. I'm in the process of trying to upgrade some npm dependencies of a project I own, and I'm getting a "conflicting peer dependency" error.
0 kommentar(er)
