Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
greenkeeper bot opened this issue May 25, 2019 · 1 comment · Fixed by #1373
Closed

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

greenkeeper bot opened this issue May 25, 2019 · 1 comment · Fixed by #1373

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 25, 2019

The devDependency ts-node was updated from 8.1.0 to 8.1.1.

🚨 View failing branch.

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).

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 26, 2019

  • The devDependency ts-node was updated from 8.1.1 to 8.2.0.

Your tests are still failing with this version. Compare changes

Release Notes for Cache FS Operations

Added

  • Expand FS cache to all file system operations

Changed

  • Pass all files to "root scripts" TypeScript compiler option to improve performance
Commits

The new version differs by 3 commits.

  • b8fd523 8.2.0
  • 1e838f7 Caching all FS operations improves perf 1.25x
  • 6dad5ad List all files in memory cache improves perf 1.4x

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants