@types peer dependencies are useless noise for flow/non-TS users, and not necessary anyway

[jedwards1211]

I know TS is winning and I'm not opposed to it at all, but Flow is entrenched in my company's codebase. Would you accept a PR to remove these peer defs? They're not necessary since @types packages track the major/minor versions of the code packages. (Though tbh that was a bad decision, because sometimes breaking changes need to made to type defs regarding parameterization etc).

Obviously peer dep warnings are not blockers but we can't have an ever-growing list of peer dep warnings, because some of them can be very important, and noise like this gets in the way of noticing the ones that matter.

[hwillson]

@jedwards1211 Please see the discussion in #3278. As soon as npm/cli#224 has been resolved, we'll get this adjusted. Thanks!

[IAmVisco]

Just wanna give my 2 cents, @types libs are used by WebStorm for static analysis and code completion even for non-TS users, so sometimes it saves few clicks.