Update eslint-plugin-import to version 2.2.0 🚀 #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukeapage
force-pushed
the
greenkeeper-eslint-plugin-import-2.2.0
branch
from
b9f168a
to
a4cee4b
Compare
lukeapage
force-pushed
the
greenkeeper-eslint-plugin-import-2.2.0
branch
from
a4cee4b
to
10b760d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
eslint-plugin-import just published its new version 2.2.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint-plugin-import.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 178 commits .
90ef48bupdate changelog for #65350d6905Merge branch 'master' into release-2.2.0314d6abprefer-default-export: handle export extensions default re-export (fixes #653)baa6b8abump utils/v2, v2.2.02517820fix unambiguous regex (#654)4744468changelog: fixed links7205904Merge remote-tracking branch 'origin/master' into release-2.1.029bc56eIgnoring flow type exports (#639)1186409first draft of release steps inRELEASE.mdbf0c8e2bump resolvers/webpack/v0.7.053cd2cdRevert "absenteeism disclaimer"954db1abump v2.1.02602b5dAdd deprecated flags to imports-first metadata (#625)cf42834changelog: rule link fixes162155eMerge remote-tracking branch 'ljharb/use_cwd'There are 178 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade