An in-range update of eslint-loader is breaking the build 🚨
greenkeeper opened this issue · 2 comments
Version 1.8.0 of eslint-loader just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | eslint-loader |
| Current Version | 1.7.1 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
1.8.0- Added: support for eslint@^4.0.0
(#178 - @Aladdin-ADD)
Commits
The new version differs by 10 commits.
579e7271.8.0d25860achore: add package-lock.json and update yarn.lockc9e9f12Revert "Added: eslintPath option (#181)"79fa82eRemove unused dep (#170)ff4737cAdded: eslintPath option (#181)553d551Merge pull request #178 from Aladdin-ADD/master605f9a6update: eslint@4.0.0343e0bfupdate: peerdep: eslint<5.0.02b76bcfupdate: eslint@v4.0.0-rc.0 & fix errorsa29006eupdate: .eslintrc
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
After pinning to 1.7.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 1.9.0 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Release Notes
1.9.0- Added:
eslintPathoption so you can provide your own eslint path.
(#183 - @trungdq88)