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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency esm was updated from 3.2.6 to 3.2.7.

🚨 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/498821218?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 21 commits.

  • 2d6962b Bump to v3.2.7.
  • 370032a Update deps.
  • 1ab39c8 Minor style nits.
  • 270a22a Extract wasmLoad() and wasmParse() from wasmCompiler().
  • 9567490 Make wasm exports settable.
  • db3d14b Ensure mocked modules work with wasm.
  • 480692e Use esmImport() for parsing wasm imports.
  • b35a959 Add test for exporting re-declared classes.
  • c22d399 Consistent use of re-.
  • e8d2d54 Add separate parse and load phases for wasm imports.
  • 1f0a5fd Minor style nits.
  • 95e20a6 Set entry.state in entry.resumeChildren().
  • e8c64b4 Style nits for entry.state in module hook.
  • 0533b90 Set more entry.state in vm hook.
  • 45051af Set state lower in src/module/internal/compile.

There are 21 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.2.6 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.