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

***
☝️ **Important announcement:** Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! [Find out how to migrate to Snyk and more at greenkeeper.io](https://greenkeeper.io)
***
## The devDependency [ts-node](https://github.com/TypeStrong/ts-node) was updated from `8.8.2` to `8.9.0`.

🚨 [View failing branch](https://github.com/coding-blocks/judge-api/compare/master...coding-blocks:greenkeeper%2Fts-node-8.9.0).

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

ts-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: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/coding-blocks/judge-api/398?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Release Notes for v8.9.0

Fixed

Fix failing tests caused by recent changes to @types/node (#1016)

Fix #945: Bump source-map-support dependency to include upstream fix for worker threads error handling (#1015) @addaleax

Fix #1004: in --scriptMode, resolve config file relative to realpath of entrypoint script (#1009)

Normalized filenames in cache to fix performance issues on Windows (#997) @sylc

Added

Add timestamps to debug logging (#994) @sylc

Docs

Improve coverage of the README (#1000) @KasparEtter

Change order of install commands in README (#993) @jacobdcastro

Mention ts-node -vv flag in issue template (#1001)

Run GHActions tests on pull requests (#1017)

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: