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

[greenkeeper[bot]]

Version 6.0.4 of ts-node was just published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	6.0.3
Type	devDependency

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

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.com/Chatie/db/builds/74321351?utm_source=github_status&utm_medium=notification)

---

Release Notes

Windows Project Resolution

Fixed

• Normalize paths for Windows before trying to resolve the project path
• Use Buffer.from instead of deprecated new Buffer

Commits

The new version differs by 3 commits.

• 98d72ce 6.0.4
• 4f40026 Use Buffer.from
• 45664e7 Fix project path resolution on Windows (#596)

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 Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 6.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

Version 6.0.5 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

Normalize More Places For Windows

Fixed

• More places to normalize for Windows to work

Commits

The new version differs by 2 commits.

• e2e3eaf 6.0.5
• 33aca82 Normalize configFileName on initialization

See the full diff