Karma fails with yarn complaining about wrong package versions being installed
In several karma build jobs we had this:
Finished in 1 minute 44.5 seconds (files took 17.67 seconds to load)
33 examples, 0 failures
warning fsevents@1.0.17: The platform "linux" is incompatible with this module.
error "assert-plus" is wrong version: expected "1.0.0", got "0.2.0"
error "async" is wrong version: expected "1.5.2", got "0.2.10"
error "bytes" is wrong version: expected "2.4.0", got "2.3.0"
error "component-emitter" is wrong version: expected "1.2.1", got "1.1.2"
error "find-up" is wrong version: expected "1.1.2", got "2.1.0"
error "glob" is wrong version: expected "7.1.1", got "5.0.15"
error "is-number" is wrong version: expected "2.1.0", got "0.1.1"
error "lodash" is wrong version: expected "4.17.4", got "3.10.1"
error "repeat-string" is wrong version: expected "1.6.1", got "0.2.2"
error "resolve" is wrong version: expected "1.2.0", got "1.1.7"
error "source-map" is wrong version: expected "0.5.6", got "0.1.43"
error "strip-bom" is wrong version: expected "2.0.0", got "3.0.0"
warning "webpack#acorn@^4.0.4" could be deduped from "4.0.11" to "acorn@4.0.11"
error "compression-webpack-plugin#async" not installed
error "babel-plugin-istanbul#find-up" not installed
error "istanbul#glob" not installed
error "karma#lodash" not installed
error "karma-webpack#lodash" not installed
error "istanbul#resolve" not installed
error "karma-webpack#source-map" not installed
error "eslint#strip-bom" not installed
error "uglify-js#async" not installed
error "compression#bytes" not installed
error "socket.io-parser#component-emitter" not installed
error "http-signature#assert-plus" not installed
error "expand-range#is-number" not installed
error "expand-range#repeat-string" not installed
error Found 26 errors.
Error: You have unmet dependencies. (`yarn check` command failed)
Run `yarn install` to install missing modules.
ERROR: Build failed: exit code 1
I wonder what happens here because:
-
karma has successfully completed—why does yarn check dependencies?nope, fixture generation has completed - Why doesn't the initial
yarn check
fail in thesetup-test-env
build job?