An in-range update of @types/node is breaking the build 🚨

## The devDependency [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped) was updated from `10.12.18` to `10.12.19`.

🚨 [View failing branch](https://github.com/benjamn/ast-types/compare/master...benjamn:greenkeeper%2F%40types%2Fnode-10.12.19).

This version is **covered** by your **current version range** and after updating it in your project **the build failed**.

@types/node is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/benjamn/ast-types/builds/485678685?utm_source=github_status&utm_medium=notification)).

---

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the failing Greenkeeper branch and the Travis CI build linked in the issue. Compare the project’s dependency configuration and build output around the update from @types/node 10.12.18 to 10.12.19. Done means the dependency update no longer causes the Travis CI build to fail.

Written by the indexing model from the issue text.