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

[greenkeeper]

Version 3.0.5 of ts-node just got published.

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

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

As ts-node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• c18331a 3.0.5
• 5cf97b1 Add --inspect-brk to known flags (#343)
• 7dfb3e3 Pin node tests at 6.x (#340)
• 633d537 chore(package): update chai to version 4.0.1 (#337)
• b751a56 Define exports and improve getTypeInfo help (#332)
• d018300 Update yn default option
• cc3bf22 Expose _ bin file for consumers to use

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 3.0.6 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

Cache Fix

Fixed

• When TypeScript was requesting a file, it was added to the cache - unfortunately a change resulted in it setting a version which lists the files used by TypeScript. TypeScript peruses this list occasionally and blows up when a non-.ts file is in the list

Commits

The new version differs by 2 commits.

• 125544f 3.0.6
• ae4b423 Set cache.contents (no version) on read request (#347)

See the full diff