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

Nobody has claimed this yet.

## The devDependency [bili](https://github.com/egoist/bili) was updated from `3.2.0` to `3.3.0`.

🚨 [View failing branch](https://github.com/maple3142/mapleutil/compare/master...maple3142:greenkeeper%2Fbili-3.3.0).

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

bili 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/maple3142/mapleutil/builds/449249673?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 2 commits.

• e5c048f Release v3.3.0


• 9810f5d update rollup

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](https://greenkeeper.io) Bot :palm_tree:

Start with the linked failing branch and Travis CI build, then inspect the bili 3.3.0 release diff, including its Rollup update. Determine why the in-range dependency breaks the build and verify that the project builds successfully with the compatible dependency configuration.

Written by the indexing model from the issue text.