chore(package): update mime v1.3.6...2.0.0

[alexander-akait]

What kind of change does this PR introduce?
Chore

Did you add tests for your changes?

not required

If relevant, did you update the README?

not required

Summary

Ref: broofa/mime#168

Does this PR introduce a breaking change?

no

Other information

not required

[ryanjadhav]

+1 thanks for updating!

[alexander-akait]

@michael-ciniawsky why blocked?

[johntron]

Just FYI in case you're unaware - NSP published a security vulnerability in the mime package used by this project. According to npm, this package gets 178,618 downloads a day. I'm sure many people can benefit from some expediency in merging this PR.

[michael-ciniawsky]

@evilebottnawi Requires node >= 6.0.0 😞

[joshwiens]

Publish as a Major & drop NodeJS 4.x support?

Taking this up with Tobias as this may be what needs to happen. Realistically, Node 4.x is EOL in April? of next year so we would be jumping the gun a bit but it's not that far off.

For those that are still on 4.x ( shouldn't be ) will have to use the existing version to retain 4.x support. It's a dev dep in 98% of the cases so the DDOS risk is minimal

[michael-ciniawsky]

@d3viant0ne mime >= v1.4.1 should be fixed aswell

[joshwiens]

Or that ^^

[joshwiens]

You will have to excuse me, i'm all for prodding people to use up to date Node versions when & wherever possible.

@evilebottnawi - Go with @michael-ciniawsky's suggestion and stick with the 1.4 version that has the DDOS fix.

[alexander-akait]

@michael-ciniawsky @d3viant0ne done

[michael-ciniawsky]

^1.4.1 😛