Update execa to version 0.5.0 🚀

[greenkeeperio-bot]

Hello lovely humans,

execa just published its new version 0.5.0.

State	Update 🚀
Dependency	execa
New version	0.5.0
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of execa.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

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 24 commits .

• 842be7c 0.5.0
• 7d88adc only set to failing test on Windows
• a6108ce use 10 megabytes per readme, not 10 mebibytes
• 9699ea2 mark failing Windows test as known failing
• 8a7a51c [BREAKING] ES2015ify and require Node.js 4
• be254ee bump npm-run-path
• a80487b fix support for the shell option in execa.shell()
• 037bfb4 remove deprecated execa.spawn() from the readme
• dbd9acd Add cleanup option (#53)
• 03964c1 ensure execa rejects and not throws when the core spawn throws and error
• e10d263 add test case for throwing on non-executables (#49)
• b15483a add tests (#48)
• ac7a103 bump cross-spawn
• 342096c fix XO lint issues
• 56a20b1 Add test for ../ paths (#43)

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

---

This pull request was created by greenkeeper.io.

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