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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency esm was updated from 3.2.16 to 3.2.17.

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

The new version differs by 17 commits.

  • e39d3d3 Bump to v3.2.17.
  • e32acb5 Update deps.
  • be7c3a1 Track state of getInfo() and readInfo().
  • d4a670f Remove setProperty() use from setSilent().
  • 333f4f1 Use more correct property descriptors instead of the setProperty() helper.
  • 027f381 Fix regression in prepareContext() that caused "constructor" to be enumerable. [closes #747]
  • 13e99b3 Make setPrototypeOf() return a boolean value.
  • bd5b394 Set prototype before assigning properties.
  • 3b52d81 Use moduleTypeOptions when FLAGS.type is "module" in src/package.js.
  • a051af6 Remove unused FLAGS.strict.
  • 16aba24 Add errors.ERR_INVALID_TYPE_FLAG().
  • 20d9e6e Cleanup src/errors.
  • eb7bcc4 Add FLAGS.esModuleSpecifierResolution and FLAGS.type.
  • 958ca2c Support package.json type field to populate esm options.
  • a901833 Prepare for new .mjs rules regarding file extension resolution.

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

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 3.2.18
  • Fixed undefined property access error for Loader.state.package.default (#752)
  • Reintroduced an improved Electron v1 fix (#750)
Commits

The new version differs by 20 commits.

  • 691f55e Bump to v3.2.18.
  • 7d83b47 Update deps.
  • a975ee2 Add Loader.state.package.default guard to prepareValue(). [closes #752]
  • 5947eb4 Revert "Remove SafeJSON."
  • c0aad80 Add toExternalObject().
  • 713171e Remove SafeJSON.
  • 41e0f0e Use SafeJSON in formatWithOptions().
  • c07d4ad Don't cache cache modules in shared.module if they use, or are used by, inspect().
  • 5cdab28 Cleanup NATIVE_SOURCE_TEXT in src/shim/function-prototype-to-string.
  • 3953a53 Add back new and improved Electron v1 fix. [closes #750]
  • 76b55af Check FLAGS.esModuleSpecifierResolution in src/module/esm/resolve-filename.
  • 86de88f Remove FLAG validation since that's handled by Node.
  • c9305df Add isCalledFromStrictCode() to shared.module cache.
  • e39f706 Use ModuleConcatenationPlugin in dev builds.
  • 4d2a3a9 Fix test262 fails.

There are 20 commits in total.

See the full diff