search

fjorgemota / jimple

Just a dependency injection container to NodeJS and to the browser using new ES6 features
MIT License
75 stars 12 forks source link

An in-range update of karma-firefox-launcher is breaking the build 🚨 #71

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency karma-firefox-launcher was updated from 1.1.0 to 1.2.0.

🚨 View failing branch.

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

karma-firefox-launcher is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/fjorgemota/jimple/builds/570020050?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 13 commits.

  • a398dae chore(release): 1.2.0
  • c1a3939 fix: Detect and kill browser process when launcher process is being used (#103)
  • c3fea39 chore: Update dependencies
  • 2e94873 chore: Add missing is-wsl entry to yarn.lock
  • b4e260e feat: Add support for running Windows Firefox from WSL
  • 2443631 chore: Add self to contributors
  • 2dca609 chore: Update dev dependencies
  • 16e6673 chore: Sort contributors list [skip ci]
  • 9e86d04 chore: Drop support for Node 6 (#98)
  • 540c1dd fix: Add -wait-for-browser
  • 6377ee3 fix: Look for other paths for Firefox Nightly on Windows and Mac
  • b9455c8 chore: Fix travis (#97)
  • 0e37f76 feat(headless): add enable remote debugging by default

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

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