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 :sparkles:
You rock!
:palm_tree:
The new version differs by 185 commits .
59520ffMerge remote-tracking branch 'origin/static-require-crash' into release-patch
e282c42(#610): Fix crash when calling require() with a number
Coverage remained the same at 100.0% when pulling 7b360c54fa96085907ae228cdeda67c6936fbaba on greenkeeper-eslint-plugin-import-2.0.1 into e85ffb53a0ae27aa868b55bc1721ee32480c9187 on master.
Coverage remained the same at 100.0% when pulling 9105ba57e00287f194c128b159c83d412ee2f5a1 on greenkeeper-eslint-plugin-import-2.0.1 into c9a1b42ac992285afdafc420d4852625c3b97415 on master.
Hello lovely humans,
eslint-plugin-import just published its new version 2.0.1.
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 185 commits .
59520ff
Merge remote-tracking branch 'origin/static-require-crash' into release-patch
e282c42
(#610): Fix crash when calling require() with a number
0aafc80
bump v2.0.1
4f3aa28
enabled no-extraneous-dependencies to avoid this in the future
e14984c
(#604): Fixed code that relied on removed dependencies
5a6c38d
Fix typo in unambiguous.md (#600)
0e6cbac
Fix single quotes in JSON example (#597)
2dec0a7
quick note on
caseSensitive
no-unresolved parama81d5bb
note on case-sensitivity changes
286c32c
changelog forgot
unambiguous
rule9880ae7
jettisoned a bunch of pre-ES6 polyfill dependencies
632e49a
v2.0.0 + utils/v1.0.0
dc3609f
Fix #529: Add rule
no-unassigned-import
1bd0650
2.0.0-beta.1
ea82630
actual dependency on eslint-module-utils 😳😅
There are 185 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade