EnvGap
`npm install` fails dependencies even with phantomjs
envgap__nathanboktae__mocha-phantomjs-195
Original GitHub issue ↗Opened 2015-07-18
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not checked yet.
- No curated issue-specific recipe or verified environment fix is available.
02 / ENVIRONMENT RECIPE
- Base commit
Not freshly verified- Manifest
package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
nathanboktae/mocha-phantomjs #195 · read the original issue
As of about a couple days ago, the following errors are popping up in all of my grunt builds using mocha-phantomjs: ``` error Windows_NT 6.3.9600 error argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" error node v0.12.7 error npm v2.11.3 error code EPEERINVALID error peerinvalid The package phantomjs does not satisfy its siblings' peerDependencies requirements! error peerinvalid Peer mocha-phantomjs@3.5.6 wants phantomjs@~1.9.1 ``` Installing `"phantomjs": "~1.9.X"` (or adding it to package.json's dependencies) doesn't change it. Here's a [travis-ci example](https://travis-ci.org/FullScreenShenanigans/FullScreenMario/builds/71586238). Edit: This seems to also be popping up elsewhere, https://github.com/google/material-design-lite/issues/1089
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]
Issue-specific recipe and runtime smoke command require review against the complete issue and repository.
Legacy reproduction is generic install-only; match the actual issue failure before admission.