search

topjun / eslint

A fully pluggable tool for identifying and reporting on patterns in JavaScript.
https://eslint.org
MIT License
0 stars 0 forks source link

An in-range update of esprima is breaking the build 🚨 #42

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 4.0.1 of esprima was just published.

Branch Build failing 🚨
Dependency esprima
Current Version 4.0.0
Type devDependency

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

esprima 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/topjun/eslint/builds/403461997?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 21 commits.

  • 0ed4b8a Stable version 4.0.1
  • cb3b14d Update ChangeLog for 4.0.1
  • 48c3c56 Fix parsing async get/set in a class
  • fcb6afb Documentation: fix the type of some nodes.
  • 03fafdf Documentation: explicit notice on supporting only JavaScript
  • 111e0ea Downstream test: ignore Recast since its master is flaky.
  • 56171bb Recognize Token.StringLiteral as a ReturnStatement argument.
  • 644423a Add missing closing brace, fix incorrect interface name
  • aef9b5a Docs: fix the type of SwitchCase's test
  • 88010df Tiny typo
  • cc67021 Correct the handling of HTML comment when parsing as a module
  • 5d0f26f Recognize Token.Template as a ReturnStatement argument.
  • 4ef74bd Test fixture: move an async test to the more proper location.
  • 807f28f Migrate to CircleCI 2.0
  • 0352cac Fix incorrect parse async with proto-identifier-shorthand

There are 21 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 6 years ago

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