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.
2991302 fixed the error message of no-deprecated-api about new Buffer() and Buffer(). Buffer.alloc and Buffer.from are supported since Node 4.5.0.
Thank you, @feross !
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 remained the same at 100.0% when pulling 8847f60e2abc9f693183036c19aa8fab3744d52d on greenkeeper-eslint-plugin-node-4.0.1 into a73f00e6ac119869267951e41b8d46d97feeb849 on master.
Hello lovely humans,
eslint-plugin-node just published its new version 4.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-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-deprecated-api
aboutnew Buffer()
andBuffer()
.Buffer.alloc
andBuffer.from
are supported since Node4.5.0
.Thank you, @feross !
The new version differs by 33 commits .
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)fb485af
Chore: use new rule format
f8a5e0b
Update: add "excluding files" feature to convertPath option (fixes #60)
390c9ec
Chore: simpify tests for es modules
719fb4d
Chore: rename .eslintrc → .eslintrc.json
ecb7c49
Breaking: drop supports for ESLint 2
ba283df
Breaking: drop supports for Node 0.x
7f37c7c
Docs: fix ruleId in exports-style.md (fixes #62)
8fd03ed
3.0.5
143f509
Fix:
no-unsupported-features
has false positive (fixes #59)4cb5fd7
Docs: fix an accidental replacement.
0714d40
3.0.4
There are 33 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.