search

Khaledgarbaya / virtual-scroll

rendering infinit amout of element using DOM
MIT License
4 stars 0 forks source link

An in-range update of mocha-jsdom is breaking the build 🚨 #48

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.2.0 of mocha-jsdom was just published.

Branch Build failing 🚨
Dependency mocha-jsdom
Current Version 1.1.0
Type devDependency

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

mocha-jsdom 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 could not complete due to an error [Details](https://travis-ci.org/Khaledgarbaya/virtual-scroll/builds/388033090?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 15 commits.

  • 05115ca v1.2.0
  • 2a40fbb Use Object.assign when available
  • c9774ca Fix lint errors
  • 93ca22f Update npm dependencies, and use yarn.lock
  • 85aa79b Merge pull request #29 from RobLoach/update-jsdom
  • 1aa046d Remove Node.js 8 from testing
  • 727f0f5 Fix Standard coding style
  • 6992984 Fix history.pushState security error
  • 5c78194 Update JSDOM in Package.json
  • 0a89148 Update Travis to Node.js 6, 7, and 8
  • 2adb4b0 docs(gitignore): Remove previously committed .idea
  • 0da5c1e fix(index.js): Change path to require old jsdom api method
  • 7c73894 fix(index.js): Change path to require old jsdom api method
  • 8c0815b Update README.md
  • c7edc92 Release v1.1.0

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 6 years ago

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