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

[greenkeeper]

Version 4.0.1 of chai just got published.

Branch	Build failing 🚨
Dependency	chai
Current Version	4.0.0
Type	devDependency

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

As chai 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

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

4.0.1 / 2017-05-31

4.0.1

Of course, any major release cannot go without a quick bugfix release shortly after - and here's ours!

Bug Fixes

• Remove package.json browser field which was mistakenly added, and caused bundler tools like Browserify or Webpack to fail as it attempted to rebundle an already bundled file. (#978, #982)

Commits

The new version differs by 2 commits.

• b38b8d7 fix: (#978) remove browser field (#982)
• d0ace69 Update supported node version badge in README FIX #975

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 🌴