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-node.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage decreased (-1.1%) to 98.883% when pulling 21709326eb555f466d1634c051b39ee7ac8662b4 on greenkeeper-eslint-plugin-node-4.2.1 into a73f00e6ac119869267951e41b8d46d97feeb849 on master.
Hello lovely humans,
eslint-plugin-node just published its new version 4.2.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-node. 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:
GitHub Release
Bug fixes
no-missing-require
andno-missing-import
rules that v4.2.0 introduced.The new version differs by 44 commits .
fb3f030
4.2.1
113c68f
Fix: no-missing-require had false positive (fixes #70)
242eeeb
4.2.0
4cc0e3f
Fix: third-party does not hide core modules
61fcbb0
Update: deprecate no-hide-core-modules (fixes #69)
8be4d96
Fix: ensure files exist with case sensitive (fixes #68)
3f03d92
4.1.0
c289f18
New: no-hide-core-modules (fixes #66)
16973f9
Chore: hide a complexity warning.
17c8ae0
Update: fix no-deprecated-api about modules which are hiding core modules (fixes #65)
91ebdf4
Update: update no-unsupported-features for Node 7.6 supports async/await (fixes #67)
1c12cae
4.0.1
2991302
Fix: New Buffer APIs are available in 4.5.0 (#64)
5fdb19a
4.0.0
6172870
Update: add ignore options to
no-deprecated-api
(fixes #58)There are 44 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.