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

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 16.1.1 of browserify was just published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	16.1.0
Type	devDependency

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

• ❌ ci/circleci Your tests failed on CircleCI Details

---

Commits

The new version differs by 9 commits.

• 25c71db 16.1.1
• fa00040 Merge pull request #1815 from browserify/ignore-perf-hooks
• a3a3e9c ignore perf_hooks
• 99f86dc Merge pull request #1811 from browserify/node-0.10-tests
• 8bbddf7 Merge pull request #1810 from al-k21/bare-fix
• d430656 explicitly mention to use ./ in require() for local files, closes #1774
• 989cc56 Fix tests on Node <0.10
• 1ab192c test/bare.js: nits
• 680d0e6 test/bare.js: fix file path

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 🌴

[greenkeeper]

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

[redgeoff]

Replaced by #112