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

[greenkeeper[bot]]

Version 3.0.3 of ts-node just got published.

Branch	Build failing 🚨
Dependency	ts-node
Current Version	3.0.2
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 :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/DouglasWebster/angular-cli-sb2-bs4/builds/228513193?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 6 commits0.

• 1856f71 3.0.3
• 491ce93 Delete config options after TypeScript parse (#321)
• f3ce9a5 Add Greenkeeper badge 🌴 (#316)
• c18692a Update Travis CI build matrix (#303)
• 8e3c7e5 Update TSLint
• 8146c91 Add info about tsconfig-paths to readme (#295)

false

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

Version 3.0.4 just got published.

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

Release Notes

Default Cache Mode

Fixed

• Always default TS_NODE_CACHE to true when unspecified

Commits

The new version differs by 2 commits0.

• 01a6be2 3.0.4
• d5849b4 Enable caching by default for programmatic usage (#323)

false

See the full diff

[DouglasWebster]

Updated after fix for failing test.