Closed greenkeeper[bot] closed 7 years ago
Update to this version instead 🚀
The new version differs by 22 commits.
8101d39
bump to 2.6.0, node/0.3.1, webpack/0.8.3, memo-parser/0.2.0
7f055ec
chore(eslint): upgrade to eslint@4
0263be4
memo-parser: require eslint >= 3.5.0 (need file path always)
b1eeade
build on node v4, again (#855)
14c501e
Merge pull request #865 from sompylasar/eslint-module-utils_tests
117717f
eslint-module-utils: Fix resolver tests for Windows paths
314ead8
eslint-module-utils: Fix test coding style
2bc4f7f
eslint-module-utils: Add test for ignore
3b4cb47
eslint-module-utils: Add test for import/resolver config checks
06695c4
eslint-module-utils: Add test for when resolver version is not specified
f65c263
eslint-module-utils: Unified test specs names to not use 'should' word
a0012f8
eslint-module-utils: Add tests for resolver versions
17d2ee9
eslint-module-utils: Add tests for hash utils
60b524b
Merge commit '3c46d308ccb462a52554257c49c374045d1a6cf7' into file_path_in_parser_options
5732742
eslint-module-utils: In tests move require stub parser to the top.
There are 22 commits in total.
See the full diff
Update to this version instead 🚀
The new version differs by 4 commits.
d9b712a
bump to v2.6.1 to bump dep on node resolver to latest 😳
4d561e3
Merge pull request #881 from futpib/named-flow-import-interface
56e60e4
Update no-extraneous-dependencies.md (#878)
9a06426
Fix flow interface imports giving false-negative with named
rule
See the full diff
Update to this version instead 🚀
The new version differs by 7 commits.
c9dd91d
bump to v2.7.0
ee5a986
changelog note for #843
0dc4451
Merge branch 'no-absolute-path-perf'
f70d127
upgraded no-absolute-path to use moduleVisitor
pattern to support all module systems
e4b8884
PR note fixes
5aa2fe0
Rename funtion reportIfMissing to reportIfAbsolute
3e8438e
Extract isAbsolutePath from importTypes helper
See the full diff
Version 2.5.0 of eslint-plugin-import just got published.
The version 2.5.0 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.
Commits
The new version differs by 27 commits.
c41ed06
bump to v2.5.0
94187a3
bump
debug
version everywhere54687d1
resolvers/webpack: v0.8.2
dac23a1
eslint-module-utils: v2.1.1 (bumping to re-publish to npm)
d92ef43
Merge pull request #696 from eelyafi/new_line_fixer
3f9e4bf
[Tests] comment out failing (and probably invalid) test
4067495
Only apps should have lockfiles.
ebaa8e3
Merge pull request #873 from lukeapage/patch-3
3268cb1
Fix documentation of newline-after-import example
3c46d30
rollback utils dependency to 2.0.0
e3a32ad
add yank note to utils change log
089f7f1
add yanking note to root change log
dfbe0e7
Upgrade debug version of eslint-module-utils (#844)
3d9c642
Merge branch 'release'
b8e9a0b
Merge pull request #861 from benmosher/release-2.4.0
There are 27 commits in total.
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: