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 🚨 #4

Open
greenkeeper bot opened this issue Jul 5, 2017 · 4 comments
Open

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

greenkeeper bot opened this issue Jul 5, 2017 · 4 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jul 5, 2017

Version 3.2.0 of ts-node just got published.

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

Release Notes Boolean Env Flags

Changed

  • Inherit boolean flags from environment
  • Remove preferGlobal warning from package.json

Added

  • Export printError utility
  • Enable debug flag for hacking
Commits

The new version differs by 7 commits.

  • d90ffba 3.2.0
  • 2e03f54 fix(package): update chalk to version 2.0.0 (#372)
  • c60d3a7 Export printError utility (#376)
  • 3f0d975 Enable debug flag for method call tracking (#377)
  • 394ddb8 Boolean flags inherit from env (#375)
  • 82effb2 Handle possibly undefined diagnostic "start"
  • 9bc3dd8 Remove preferGlobal from package.json

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
Copy link
Author

greenkeeper bot commented Jul 5, 2017

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 20, 2017

Version 3.2.1 just got published.

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

Commits

The new version differs by 5 commits.

  • c69b242 3.2.1
  • 477e705 Fix source map output for .tsx files (#395)
  • e9e9621 fix(package): update v8flags to version 3.0.0 (#390)
  • 23b5036 Document ability to pass paths to --project (#392)
  • 6748fa3 Add note about node.js CLI options

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 24, 2017

Version 3.2.2 just got published.

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

Release Notes Improve Source Map Inline Perf

Fixed

  • Fixed inline source map replacement for large files
Commits

The new version differs by 2 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 24, 2017

Version 3.3.0 just got published.

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

Release Notes Validate Cache Files

Changed

  • Validate cache file endings before using
Commits

The new version differs by 2 commits.

  • 668e9ef 3.3.0
  • 365d53d Validate cache file contents before use (#394)

See the full diff

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

No branches or pull requests

0 participants