consider automating dep updates

[adnasa]

Naturally, since it's been a while since we continued on maintaining this project, a lot of our packages went (way) outdated.

with #184 merged in, the next is of course of to upgrade babel-* -> @babel/* and webpack. once these upgrades are done, we should start considering automating the update of deps; with the exception of webpack.

Upgrading webpack regularly could require constant re-factoring for builds to pass, which can be time consuming. we can certain automate updates of this package, but only get the notification on a major upgrade.

---

There are a few options to automation: greenkeeper vs renovate.
I for one, highly appreciate renovate due to its respect for peer dependency, and not to mention scheduled updates.

---

putting this issue on hold, until we finished @babel x webpack upgrade 😉

[vutran]

I'm down for this. I've used greenkeeper in the past but haven't tried renovate yet. One thing I disliked about automatic dependency updates is receiving too many emails/notifs but it does make sense as we scale out so we can avoid maintaining these small things.