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 Notesv7.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.
Note some assertion methods such as assert.equal are deprecated. Use stricter methods such as assert.strictEqual or the strict mode (assert.strict) instead.
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.
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).
It fixed false positive that the node/no-unsupported-features/node-builtins reports the process.emitWarning method on Node.js >=6 <8. It was supported since Node.js 6.0.0.
Version 7.0.0 of eslint-plugin-node was just published.
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.0Breaking changes
>=6
.>=4.19.1
. (thenode/recommended
preset is supporting only ESLint>=5.0.0
)node/recommended
config.parserOptions.ecmaVersion
to2019
from2018
.plugins: ["node"]
.10.6.0
.assert.equal
are deprecated. Use stricter methods such asassert.strictEqual
or the strict mode (assert.strict
) instead.New rules
Buffer
orrequire("buffer").Buffer
consistently.console
orrequire("console")
consistently.process
orrequire("process")
consistently.URLSearchParams
orrequire("url").URLSearchParams
consistently.URL
orrequire("url").URL
consistently.Deprecated rules
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/*
rules217411d
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: