search

jacktuck / unfurl

Metadata scraper with support for oEmbed, Twitter Cards and Open Graph Protocol for Node.js :zap:
MIT License
475 stars 51 forks source link

An in-range update of nyc is breaking the build 🚨 #25

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 11.3.0 of nyc was just published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.2.1
Type devDependency

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

nyc 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/jacktuck/unfurl/builds/296124558?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 12 commits.

  • d85118c chore(release): 11.3.0
  • 7792733 chore: explicitly update istanbul dependencies (#698)
  • 222a3d0 chore: slight difference in pinning logic, based on @ljharb's advice
  • f04b7a9 feat: add option to hook vm.runInContext (#680)
  • cdfdff3 feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
  • a413f6a chore: upgrade to yargs 10 (#694)
  • 10125aa docs: fix reporters link
  • f5089ca docs: added examples of coverage reports (#656)
  • af281e7 chore: update spawn-wrap to 1.4.0 (#692)
  • a685f7c docs: missing options prefix -- in front of check-coverage (#695)
  • f31d7a6 feat: allow instrument-only to produce sourcemaps (#674)
  • 425c0fd chore: ignore package-lock.json (#683)

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