The version 6.0.1 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-node.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv6.0.1
Bug fixes
234703c fixed a regression that node/no-unsupported-features crashes if engines field exists but engines.node field doesn't exist in package.json (#109). Thanks @ZauberNerd !
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 93.382% when pulling 443edf98bf69db9015493f70293868f5c0495875 on greenkeeper/eslint-plugin-node-6.0.1 into d938ed91f981c32d8ca214a3200cd8a096299809 on master.
Coverage remained the same at 93.382% when pulling 443edf98bf69db9015493f70293868f5c0495875 on greenkeeper/eslint-plugin-node-6.0.1 into d938ed91f981c32d8ca214a3200cd8a096299809 on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 6.0.1 of eslint-plugin-node was just published.
The version 6.0.1 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-node.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v6.0.1Bug fixes
node/no-unsupported-features
crashes ifengines
field exists butengines.node
field doesn't exist in package.json (#109). Thanks @ZauberNerd !Commits
The new version differs by 3 commits.
5260039
6.0.1
9ccc91d
Chore: add a test for #109
234703c
Fix: ensure "version" always has a valid value in parseOptions (#109)
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: