search

Kronos-Integration / test-step

kronos-step testing support with ava
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

An in-range update of esm is breaking the build 🚨 #368

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency esm was updated from 3.0.84 to 3.1.0.

🚨 View failing branch.

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

esm 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.org/Kronos-Integration/test-step/builds/480462358?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 424 commits.

  • 33ee0ac Bump to v3.1.0.
  • a84a624 Update deps.
  • 9110dd2 Cleanup readme.
  • 7adc4fd Make Package exposable through require().
  • c149647 Newline nit.
  • 885afd0 Add circular entry to esm loader fake compile data.
  • c7a5a1f Update getNativeSource() for latest Node master branch.
  • 8a3d1ce Remove unneeded catch param.
  • 8e8c354 Add more entry and package cache guards to env modules.
  • b77cf1a Don't cache entry or package instances in isSideloaded().
  • f326152 Fix wasm support regression.
  • fd47bfc Reset entry validation for repl.
  • 7869529 Remove validation dead code from vm hook for now.
  • 6ac3788 Cleanup done() handler.
  • 34c0624 Avoid multi-var assignments.

There are 250 commits in total.

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] commented 5 years ago

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