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

[greenkeeper]

Version 2.3.3 of debug just got published.

Branch	Build failing 🚨
Dependency	debug
Current Version	2.3.2
Type	dependency

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

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

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

Commits

The new version differs by 7 commits .

• 3ad8df7 Release 2.3.3
• 8e09edf browser: whitespace
• 3491ad6 Merge pull request #195 from jalleyne/master
• 2caf4ef Merge pull request #331 from levithomason/patch-1
• 20c37fd fix(browser): do not override ls debug if found
• a746d52 don't create an empty object when no process
• 6830d9f Catch JSON stringily errors.

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 🌴

[greenkeeper]

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

[pzrq]

See both #139 (not an issue if we update debug so let's update) and #138 (need to do download before starting the test timers as a ~100MB download often takes more than 10s).