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:
    • node/no-unsupported-features/es-builtins
    • node/no-unsupported-features/es-syntax
    • node/no-unsupported-features/node-builtins.
• It updated the node/no-deprecated-api rule to support Node.js up to 10.6.0.
  • Note some assertion methods such as assert.equal are deprecated. Use stricter methods such as assert.strictEqual or the strict mode (assert.strict) instead.

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

v6.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 !

v6.0.0

Breaking Changes

• 49c060a updated node/no-unsupported-features rule to support ES2018 syntactic features. Now the rule recognizes the following syntax:
  • Rest/Spread Proeprties (since Node.js 8.3.0)
  • Illegal Escape Sequences in Taggled Templates (since Node.js 9.0.0)
  • RegExp 's' Flag (since Node.js 9.0.0)
  • RegExp Lookbehind Assertions (since Node.js 9.0.0)
  • RegExp Named Capture Groups (since Node.js 10.0.0)
  • RegExp Unicode Property Escapes (since Node.js 10.0.0)
  • Asynchronous Iteration (since Node.js 10.0.0)
• 400e20a updated node/no-deprecated-api rule to support new deprecated APIs. Now the rule recognizes the following APIs:
  • async_hooks.currentId
  • async_hooks.triggerId
  • module._debug
  • path._makeLong
  • tls.parseCertString
• e8d757b updated plugin:node/recommended preset.

v5.2.0

Bug fixes

• e7878e9 fixed no-deprecated-api that has overlooked GLOBAL and root global variables which are deprecated in Node.js 6.0.0. (#92)

v5.1.1

Bug fixes

• 0295a7f fixed that no-deprecated-api crashs on self-assigning of objects which have deprecated API. (#87)

v4.2.3

#87 was backported to v4.

Bug fixes

• 2297787 fixed that no-deprecated-api crashs on self-assigning of objects which have deprecated API. (#87)

v5.1.0

Enhancements

• 47e0cc2 added resolvePaths option to no-missing-require and no-missing-import rules. You can customize paths to try for when resolving importing.

v5.0.0

Notable changes are 2:

1. Node.js 8 support were added.
2. The check of extraneous packages were separated from no-unpublish-import rule and no-unpublish-require rule.

Breaking changes

• 3387336 updated no-unsupported-features rule for Node.js 8.
  • Node.js 8 newly supports trailing commas in functions.
  • This rule went to use 4.0.0 if you don't specify the node version. It has been 0.10.0 before.
  • This rule went to warn SharedArrayBuffer and Atomics. Currently any versions of Node.js don't support those variables.
• 0e487f9 updated no-deprecated-api rule for Node.js 8.
  • Node.js 8 deprecated vm.runInDebugContext().
  • Additionally, Node.js 8 made the official page about deprecated APIs. I realized this rule had been lacking the check of some deprecated APIs. I added those.
• d4e6bc4 removed the check about extraneous packages from no-unpublish-import rule and no-unpublish-require rule.
  • The extraneous packages are checked by no-extraneous-import rule and no-extraneous-require rule.

New rules

• a75c638 added 2 new rules, no-extraneous-import and no-extraneous-require. Those rules report require() expressions or import declarations if those import extraneous packages.
  • Those behavior were extracted from no-unpublished-require and no-unpublished-import.

Bug fixes

• deb4f55 fixed a bug of no-unsupported-features about semver comparison. (#78)

v4.2.2

Bug fixes

• b2c6877 fixed a bug of node/no-unpublished-require and node/no-unpublished-import. Those had been handling some files such as raedme.js as published files always even if the files exist in subdirectories. npm always publishes such files of only top level.
  Thank you, @platinumazure !

v4.2.1

Bug fixes

• 113c68f fixed false positive of no-missing-require and no-missing-import rules that v4.2.0 introduced.