An in-range update of karma-chrome-launcher is breaking the build 🚨

[greenkeeper]

Version 2.2.0 of karma-chrome-launcher just got published.

Branch	Build failing 🚨
Dependency	karma-chrome-launcher
Current Version	2.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As karma-chrome-launcher is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ ci/circleci Your tests failed on CircleCI Details

---

Release Notes

v2.2.0

Features

• add ChromiumHeadless (7a12021)

Commits

The new version differs by 6 commits.

• b01cea1 chore: release v2.2.0
• 40e96e2 chore: update contributors
• 998824d Merge pull request #135 from ishitatsuyuki/chromium-headless
• 7a12021 feat: add ChromiumHeadless
• 96d84aa Merge pull request #126 from mgol/patch-1
• 2a02494 refactor: remove incorrect comment

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.