An in-range update of eslint-plugin-node is breaking the build 🚨

## The devDependency [eslint-plugin-node](https://github.com/mysticatea/eslint-plugin-node) was updated from `9.0.1` to `9.1.0`.

🚨 [View failing branch](https://github.com/brysgo/graphql-path/compare/master...brysgo:greenkeeper%2Feslint-plugin-node-9.1.0).

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

eslint-plugin-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

- ❌ **ci/circleci:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/brysgo/graphql-path/145?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Commits

The new version differs by 3 commits.

• 7ce77f9 🔖 9.1.0


• e5aee3c 🐛 support * in engines.node (fixes #155)


• fd9d19d ✨ no-deprecated-api adheres to targeted node version (fixes #141) (#164)

See the full diff

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 by reproducing the failed CircleCI build from the Greenkeeper failing branch and inspect the dependency update from eslint-plugin-node 9.0.1 to 9.1.0. Done means the project build and tests pass with the update, or the dependency range is corrected if that version cannot be supported.

Written by the indexing model from the issue text.