die folgende Ausgabe von einem Vanille Unter npm install
:Lese peerinvalid Ausgang
npm ERR! peerinvalid The package grunt does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.5
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.4.x
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.4.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.4.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.0
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.5
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.5
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.4.0
Wie man die Abhängigkeit Version Probleme von package.json nicht diagnostizieren, die die folgenden Abhängigkeiten:
"grunt": "0.4.5",
"grunt-bower-concat": "^0.6.0",
"grunt-bower-install": "^1.6.0",
"grunt-bower-task": "^0.4.0",
"grunt-contrib-connect": "0.11.2",
"grunt-contrib-copy": "^0.8.2",
"grunt-contrib-less": "^1.0.1",
"grunt-contrib-watch": "0.4.0",
"grunt-processhtml": "^0.3.8",
"grunt-lesslint": "^1.4.0",
"grunt-tslint": "^2.4.0",
"grunt-typescript": "^0.8.0",
"matchdep": "~0.1.1",
"tslint": "^2.4.2"
Die peerDependencies haben die folgenden eindeutigen Regeln:
~0.4.5 :: True, grunt dependency is hard-coded as exactly 0.4.5
>=0.4.x :: True, 0.4.5 >= 0.4.x
>=0.4.0 :: True, 0.4.5 >= 0.4.0
~0.4.0 :: True, 0.4.5 is a patch of 0.4.0
Alle diese bestehen für die angegebene Version der grunt
Abhängigkeit. Warum klagen NPM noch?