Oftentimes you can find breaking change about dependency like this.
In that case, you can check if there is a higher version of packageB that requires version 4.2.0 of packageA in the npm or github. Good news is that in some cases, packageB is just not keeping up with packageA and maintainer of packageB is trying hard to raise the peer dependency of packageA to 4.x.x. So you can resolve this error by downgrading packageA to 3.x.x, but usually you don`t want to downgrade the package. This means you installed version 4.2.0 of packageA, but needs version 3.x.x of pakageA.
UNMET PEER DEPENDENCY WARN requires a peer of but none was installed. This answer doesn’t apply all cases, but if you can’t solve the error by simply typing npm install It is one of the reasons to upgrade to v7.Īlso this page explains the rationale of peer dependencies very well. From npm v7.0.0, npm automatically installs peer dependencies.
0 kommentar(er)
