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

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The dependency clsx was updated from `1.1.0` to `1.1.1`.

🚨 View failing branch.

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

clsx is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **build (12.x):** There are 1 failures, 0 warnings, and 0 notices.

Commits

The new version differs by 17 commits.

c5b2b21 1.1.1
fd1533f chore: update badges
0fb6d98 chore(action): include Node 6.x w/ conditionals
5e92fdf debug(action): drop pnpm :'(
768ffab fix(action): pnpm loses include context
866620d debug(action): tweak cache settings
883363b fix(action): remove lerna steps
64af363 chore: import Action script
0287e40 chore: tests w/ esm hook
3c6aa3f chore: lock devdeps
75053c0 chore: update benchmark results
7e8c75e chore: update module size
08a5a7f fix: reorder typeof checks
019ec02 fix: guard all toVal calls;
4fa8811 fix: use falsey check from arguments;

There are 17 commits in total.

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 Bot :palm_tree:

walleXD / reactrolysis