search

yeldiRium / st3k101

UNMAINTAINED.
2 stars 1 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency esm was updated from 3.1.1 to 3.1.2.

🚨 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **ci/circleci: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/yeldiRium/st3k101/349?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
Commits

The new version differs by 104 commits.

  • af45c02 Bump to v3.1.2.
  • 7bc32e5 Update package-lock.json.
  • dc49c5b Avoid re-preloading esm itself.
  • 1e3909f Ensure entry.type is deferred in Entry.get().
  • f2f7b66 Ensure namespace objects of cyclical CJS modules are handled appropriately.
  • 49ebe0c Minor cleanup of entry.
  • 93c8469 Minor module hook cleanup.
  • 6c8f298 Minor misc test cleanup.
  • 238f1a8 Add parsing state to wasm ext compiler.
  • d51ddac Cleanup setting entry.state.
  • f82c847 Cleanup reassociate branch of module/proto/load.
  • 93f6ca1 Cleanup compileFallback() and handle returns consistently in module hook.
  • 66f8535 Don't overwrite/wrap module._compile on the execution run.
  • 1e4dbcc Cleanup find-path test.
  • 15307b8 Simplify sinon scenario test.

There are 104 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:

yeldiRium commented 5 years ago

What? The branch did not actually fail. Maybe Greenkeeper wasn't patient enough.