-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of eslint-plugin-import is breaking the build 🚨 #50
Comments
After pinning to 2.16.0 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 changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 14 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 46 commits.
There are 46 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 46 commits.
There are 46 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 14 commits.
See the full diff |
The devDependency eslint-plugin-import was updated from
2.16.0
to2.17.0
.🚨 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 61 commits.
0499050
bump to v2.17.0
f479635
[webpack] v0.11.1
8a4226d
Merge pull request #1320 from bradzacher/export-ts-namespaces
988e12b
fix(export): Support typescript namespaces
70c3679
[docs] make rule names consistent
6ab25ea
[Tests] skip a TS test in eslint < 4
405900e
[Tests] fix tests from #1319
2098797
[fix]
export
: false positives for typescript type + value export70a59fe
[fix] Fix overwriting of dynamic import() CallExpression
e4850df
[ExportMap] fix condition for checking if block comment
918567d
[fix]
namespace
: add check for null ExportMap2d21c4c
Merge pull request #1297 from echenley/ech/fix-isBuiltIn-local-aliases
0ff1c83
[dev deps] lock typescript to
~
, since it doesn’t follow semver40bf40a
[*] [deps] update
resolve
28dd614
Merge pull request #1304 from bradennapier/feature/typescript-export-type
There are 61 commits in total.
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: