This repository has been archived by the owner on Feb 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
An in-range update of eslint-plugin-import is breaking the build 🚨 #8
Labels
Comments
After pinning to 2.18.0 your tests are passing again. Downgrade this dependency 📌. |
Your tests are still failing with this version. Compare changes |
coderbyheart
added a commit
that referenced
this issue
Jul 23, 2019
Fixes #12 An in-range update of eslint-plugin-react is breaking the build Fixes #11 An in-range update of @typescript-eslint/parser is breaking the build Fixes #10 An in-range update of @typescript-eslint/eslint-plugin is breaking the build Fixes #9 An in-range update of eslint is breaking the build Fixes #8 An in-range update of eslint-plugin-import is breaking the build Fixes #7 An in-range update of aws-amplify is breaking the build Fixes #6 An in-range update of aws-amplify-react is breaking the build Fixes #5 An in-range update of husky is breaking the build Fixes #4 An in-range update of eslint-plugin-flowtype is breaking the build Fixes #3 An in-range update of aws-sdk is breaking the build Fixes #2 An in-range update of @types/node is breaking the build
Merged
coderbyheart
added a commit
that referenced
this issue
Jul 23, 2019
Fixes #12 An in-range update of eslint-plugin-react is breaking the build Fixes #11 An in-range update of @typescript-eslint/parser is breaking the build Fixes #10 An in-range update of @typescript-eslint/eslint-plugin is breaking the build Fixes #9 An in-range update of eslint is breaking the build Fixes #8 An in-range update of eslint-plugin-import is breaking the build Fixes #7 An in-range update of aws-amplify is breaking the build Fixes #6 An in-range update of aws-amplify-react is breaking the build Fixes #5 An in-range update of husky is breaking the build Fixes #4 An in-range update of eslint-plugin-flowtype is breaking the build Fixes #3 An in-range update of aws-sdk is breaking the build Fixes #2 An in-range update of @types/node is breaking the build
🎉 This issue has been resolved in version 1.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The devDependency eslint-plugin-import was updated from
2.18.0
to2.18.1
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-import 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
Commits
The new version differs by 14 commits.
b51aa2f
Bump to v2.18.1
32704da
fix: Improve parse perf when using
@typescript-eslint/parser
3b21de6
[Tests] extract common "get parser" logic into test helpers
f4e3f1b
prefer-default-export: don't warn on TypeAlias & TSTypeAliasDeclaration
1caa402
[Fix]
no-unused-modules
: Exclude package "main"/"bin"/"browser" entry points22d5440
[fix]
export
: false positive for typescript overloads5abd5ed
[Tests] temporarily disable these failing tests in eslint < 4
752dcd5
[Tests] add missing
--no-save
to time travel scriptd3a3fa5
[Refactor]
no-extraneous-dependencies
: remove the last bit of lodash8a38fd4
[Refactor]
no-extraneous-dependencies
: useArray.isArray
instead of lodashc5078ad
[Refactor]
importType
: remove use ofcond
118afd4
no-deprecated: don't run tests for typescript-eslint-parser against ESLint <4
6512110
fix tests for node 4 + fixed lint issues
bb9ba24
no-deprecated TS tests (#1315)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: