Update eslint-plugin-node to the latest version 🚀

Version 7.0.0 of eslint-plugin-node was just published.

Dependency	eslint-plugin-node
Current Version	6.0.1
Type	devDependency

The version 7.0.0 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

v7.0.0

Breaking changes

It dropped the support of Node.js 4. Now it requires >=6.
It dropped the support of ESLint 3. Now it requires >=4.19.1. (the node/recommended preset is supporting only ESLint >=5.0.0)
It updated the node/recommended config.
- changed parserOptions.ecmaVersion to 2019 from 2018.
- added plugins: ["node"].
- removed a deprecated rule: node/no-unsupported-features.
- added three new rules:
It updated the node/no-deprecated-api rule to support Node.js up to 10.6.0.

New rules

node/no-unsupported-features/es-builtins ... disallow unsupported ECMAScript built-in globals on the configured Node.js version.
node/no-unsupported-features/es-syntax ... disallow unsupported ECMAScript syntax on the configured Node.js version.
node/no-unsupported-features/node-builtins ... disallow unsupported Node.js built-in modules and globals on the configured Node.js version.
node/prefer-global/buffer ... enforce the use of either Buffer or require("buffer").Buffer consistently.
node/prefer-global/console ... enforce the use of either console or require("console") consistently.
node/prefer-global/process ... enforce the use of either process or require("process") consistently.
node/prefer-global/url-search-params ... enforce the use of either URLSearchParams or require("url").URLSearchParams consistently.
node/prefer-global/url ... enforce the use of either URL or require("url").URL consistently.

Deprecated rules

node/no-unsupported-features was replaced by node/no-unsupported-features/es-builtins and node/no-unsupported-features/es-syntax.

Chore

I extracted the logic which detects certain globals and modules and those properties to the eslint-utils package. I wish it to be useful for your ESLint plugins.

All commits: 5260039...890ee63

Commits

The new version differs by 48 commits.

890ee63 7.0.0
7ab875a Chore: refactoring no-deprecated-api
fa25150 Chore: refactoring for no-unsupported-features/*
8f25248 Chore: refactoring for prefer-global/*
4dd9baf Chore: move data into rules
069efe9 Breaking: update 'no-deprecated-api' rule
7137055 7.0.0-beta.0
a42d38e Docs: update README.md
1946d61 Breaking: update recommended.json
cb8f504 Update: add ES2019 support in 'no-unsupported-features/es-syntax'
3d79333 New: prefer-global/* rules
217411d Chore: re-organize no-unsupported-features (fixes #118)
b02dcef New: no-unsupported-features/worker_threads rule (refs #118)
65cbc08 New: no-unsupported-features/vm rule (refs #118)
222f6c0 New: no-unsupported-features/v8 rule (refs #118)

There are 48 commits in total.

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:

html-next / ember-hammertime