search

katoy / node-xlsx

XLSX.js is a JavaScript library for converting the data in base64 XLSX files into JavaScript objects - and back! Please see the below link for more information. If you know of a page that contains useful information about XLSX.js, please contact us so that we can include a link here.
http://blog.innovatejs.com/?page_id=7
Other
10 stars 2 forks source link

An in-range update of qunit-tap is breaking the build 🚨 #2

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency qunit-tap was updated from 1.5.0 to 1.5.1.

🚨 View failing branch.

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

qunit-tap 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/katoy/node-xlsx/builds/522552516?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 58 commits.

  • ead1ba4 1.5.1
  • ac30ba0 docs(README): changelog for 1.5.1
  • b3cdb5d docs(README): update usage
  • 40c9b11 chore(package): reduce package size
  • 2729143 chore(package): use SPDX license expression to be compatible with new npm
  • 39dc23b chore(package): apply fixpack
  • a81d408 chore(qunit-tap): migrate to 2.0.0 style
  • 57c0faa docs(README): support QUnit 2.0.0
  • 44f979d Merge pull request #12 from twada/qunit-2.0.0
  • a33f1dc test(qunit-tap): use grep instead of bash specific feature
  • 9a62ea4 chore(travis): drop v0.8 and add Node v6 to CI
  • 9416a32 test(qunit-tap): run phantomjs suite on CI
  • f3f7a60 test(qunit-tap): reorganize phantomjs suite
  • 0dc8126 chore(qunit-tap): dealing with arg handling of newer phantomjs
  • 3d0336a chore(qunit-tap): add QUnit 2.0.0 to test suite

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