Open greenkeeper[bot] opened 7 years ago
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.
Your tests are still failing with this version. Compare the changes 🚨
eslintPath
option so you can provide your own eslint path.
Version 1.8.0 of eslint-loader just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Nebo15/react-nebo15-events/builds/243161535?utm_source=github_status&utm_medium=notification)Release Notes
1.8.0(#178 - @Aladdin-ADD)
Commits
The new version differs by 10 commits.
579e727
1.8.0
d25860a
chore: add package-lock.json and update yarn.lock
c9e9f12
Revert "Added: eslintPath option (#181)"
79fa82e
Remove unused dep (#170)
ff4737c
Added: eslintPath option (#181)
553d551
Merge pull request #178 from Aladdin-ADD/master
605f9a6
update: eslint@4.0.0
343e0bf
update: peerdep: eslint<5.0.0
2b76bcf
update: eslint@v4.0.0-rc.0 & fix errors
a29006e
update: .eslintrc
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: