chore: Update tmp to the latest version 🚀

[greenkeeper]

Version 0.0.33 of tmp just got published.

Dependency	tmp
Current Version	0.0.30
Type	dependency

The version 0.0.33 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 tmp.
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.

---

Commits

The new version differs by 75 commits.

• 0900dd5 Releasing v0.0.33
• 9f4071e Merge pull request #147 from raszi/gh-146
• fb3801a Merge pull request #149 from raszi/gh-148
• cd3c5b2 fix #148 fileSync must honor detachDescriptor and discardDescriptor options
• a9769f9 fix #146 with name option try at most once to get a unique tmp name
• 8f73d89 Merge branch 'gh-133'
• 6c2f762 fix #134
• f8db66b Merge pull request #135 from raszi/gh-133
• bb31918 fix #133, #134
• 0499864 Merge pull request #128 from raszi/gh-127
• fa52445 fix #127 add reference to tmp-promise
• d72a47a Merge pull request #123 from madnight/patch-1
• 7518402 Update tmp.js MIT license header to 2017
• eca328a Merge pull request #122 from raszi/gh-118
• 24bff86 add issue template

There are 75 commits in total.

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 🌴

[coveralls]

Coverage remained the same at 100.0% when pulling fde2420 on greenkeeper/tmp-0.0.33 into e82fb5f on master.

[coveralls]

Changes Unknown when pulling 979345a on greenkeeper/tmp-0.0.33 into ** on master**.