Eslint Plugin Node Versions Save

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: 5260039c77fd7e6368c1a5808f90462e5beec6f3...890ee63e98ef95ec5a27f50f42188102526d81b1

Bug fixes

• 234703cc58d1d8ebfdf0be367d958bf6682b299f 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 !

Breaking Changes

• 49c060a7f7fcb5c33712914ce75bd499cf7e1340 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)
• 400e20a00a1620f986eb91317d6d26e1b049f8dd 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
• e8d757b97ac571d456085e9103dc7b9cbd9500c7 updated plugin:node/recommended preset.

Bug fixes

• e7878e9cf66ce125f0c9617663d3e92db03fe454 fixed no-deprecated-api that has overlooked GLOBAL and root global variables which are deprecated in Node.js 6.0.0. (https://github.com/mysticatea/eslint-plugin-node/issues/92)

Bug fixes

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

#87 was backported to v4.

Bug fixes

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

Enhancements

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

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

• 3387336175d0ac5e5d47650218667320cabb3a0e 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.
• 0e487f9aa7f5548e407f04f84446c9613203c962 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.
• d4e6bc4bc8442208c81beee18b78e94cad149a47 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

• a75c63800e8e695aa836736d4ddc6c84d9076ee2 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

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

Bug fixes

• b2c68771449851c2a3473dddba387457a417e023 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 !

Bug fixes

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