formidable@1.1.1 breaks build ⚠️

[greenkeeperio-bot]

Hello lovely humans,

formidable just published its new version 1.1.1.

State	Failing tests ⚠️
Dependency	formidable
New version	1.1.1
Type	devDependency

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

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

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!

🌴

---

GitHub Release

• Fix DeprecationWarning about os.tmpDir() (Christian)
• Update buffer.write order of arguments for Node 7 (Kornel Lesiński)
• JSON Parser emits error events to the IncomingForm (alessio.montagnani)
• Improved Content-Disposition parsing (Sebastien)
• Access WriteStream of fs during runtime instead of include time (Jonas Amundsen)
• Use built-in toString to convert buffer to hex (Charmander)
• Add hash to json if present (Nick Stamas)
• Add license to package.json (Simen Bekkhus)

---

This pull request was created by greenkeeper.io.

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

[coveralls]

Coverage remained the same at 97.927% when pulling 8f7286d on greenkeeper-formidable-1.1.1 into 03444d2 on master.