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

[greenkeeper]

The devDependency brfs was updated from 2.0.1 to 2.0.2.

🚨 View failing branch.

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

brfs 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/appveyor/branch: AppVeyor build failed (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).

---

Commits

The new version differs by 4 commits.

• 660f6d8 2.0.2
• eb26fec Merge pull request #93 from jagonzalr/pr/update/static-val-version
• 434cc8b Update static-module from 3.0.0 to 3.0.2
• 8fafcf5 Remove stray console.log

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 2.0.1 your tests are passing again. Downgrade this dependency 📌.

[alxhotel]

The branch greenkeeper/brfs-2.0.2 is now passing the tests. It can be merged.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[feross]

Looks like we can just ignore this issue since master is passing now.