karma-nightmare An in-range update of browserify is breaking the build 🚨

The devDependency browserify was updated from `16.2.3` to `16.3.0`.

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

browserify 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 is in progress (Details).
✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
❌ wercker/build: Wercker pipeline failed (Details).

Commits

The new version differs by 8 commits.

9824fae 16.3.0
9e3397b Add http2 to builtins (#1913)
d2ade25 Add http2 to builtins
876182d Tweak license text so Github detects it correctly
16f82a7 Update license (#1906)
7ad39ce Merge pull request #1139 from insidewarehouse/resolve-exposed-folders
f13b713 when a module is exposed, it should still resolve the way it would normally do, i.e. with/without extension and directories should fall back to index, and index from a directory should be accepted with/without extension too
8f80729 Update license

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot :palm_tree:

Jul 05 '19 15:07 greenkeeper[bot]

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

Jul 05 '19 15:07 greenkeeper[bot]