Hello lovely humans,

debug just published its new version 2.3.2.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

The new version differs by 51 commits .

• 1c6f458 Release 2.3.2
• 56fd336 be super-safe in index.js as well
• 0b6ca27 fix(browser): should check whether process exists
• 6b45c3a Release 2.3.1
• acd3f5f Merge pull request #324 from paulcbetts/electron-compat
• 6d2cd13 Save a stat
• dc86779 If we're in Electron, try to fallback to process.env.DEBUG if we've got it
• 2ba1323 Wire it up
• d267111 Add a switch to flip between electron and node
• 2f9dc36 Merge pull request #321 from fengmk2/remove-lockfile
• 310ae22 Library should not contains lockfile
• 475e7b3 some random optimizations
• 54b1a5a Merge pull request #252 from gimre/patch-1
• 8e5a6b3 2.3.0
• d887d93 updated contributors

There are 51 commits in total. See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}