diff --git a/docs/rules/no-deprecated-api.md b/docs/rules/no-deprecated-api.md index 40b45072..aea0be52 100644 --- a/docs/rules/no-deprecated-api.md +++ b/docs/rules/no-deprecated-api.md @@ -151,12 +151,12 @@ For example of `package.json`: "name": "your-module", "version": "1.0.0", "engines": { - "node": ">=8.0.0" + "node": ">=16.0.0" } } ``` -If you omit the [engines] field, this rule chooses `>=8.0.0` as the configured Node.js version since `8` is the minimum version the community is maintaining (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). +If you omit the [engines] field, this rule chooses `>=16.0.0` as the configured Node.js version since `16` is the active lts (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). ### Options @@ -166,7 +166,7 @@ This rule has 4 options. { "rules": { "n/no-deprecated-api": ["error", { - "version": ">=8.0.0", + "version": ">=16.0.0", "ignoreModuleItems": [], "ignoreGlobalItems": [] "ignoreIndirectDependencies": true diff --git a/docs/rules/no-unsupported-features/es-builtins.md b/docs/rules/no-unsupported-features/es-builtins.md index 3e087b0d..764242d4 100644 --- a/docs/rules/no-unsupported-features/es-builtins.md +++ b/docs/rules/no-unsupported-features/es-builtins.md @@ -24,9 +24,9 @@ This rule gets the supported Node.js version range from the following, falling b 1. Rule configuration `version` 2. ESLint [shared setting](http://eslint.org/docs/user-guide/configuring.html#adding-shared-settings) `node.version` 3. `package.json` [`engines`] field -4. `>=8.0.0` +4. `>=16.0.0` -The default version is `8.0.0` because it's the minimum version the community is maintaining (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). +If you omit the [engines] field, this rule chooses `>=16.0.0` as the configured Node.js version since `16` is the active lts (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). For Node.js packages, using the [`engines`] field is recommended because it's the official way to indicate support: @@ -35,7 +35,7 @@ For Node.js packages, using the [`engines`] field is recommended because it's th "name": "your-module", "version": "1.0.0", "engines": { - "node": ">=8.0.0" + "node": ">=16.0.0" } } ``` @@ -47,7 +47,7 @@ For [Shareable Configs](https://eslint.org/docs/latest/developer-guide/shareable ```json { "n/no-unsupported-features/es-builtins": ["error", { - "version": ">=8.0.0", + "version": ">=16.0.0", "ignores": [] }] } @@ -159,7 +159,7 @@ For Example: { "settings": { "node": { - "version": ">=8.0.0", + "version": ">=16.0.0", } }, "rules": { diff --git a/docs/rules/no-unsupported-features/es-syntax.md b/docs/rules/no-unsupported-features/es-syntax.md index cf7771db..2fc64aac 100644 --- a/docs/rules/no-unsupported-features/es-syntax.md +++ b/docs/rules/no-unsupported-features/es-syntax.md @@ -27,9 +27,9 @@ This rule gets the supported Node.js version range from the following, falling b 1. Rule configuration `version` 2. ESLint [shared setting](http://eslint.org/docs/user-guide/configuring.html#adding-shared-settings) `node.version` 3. `package.json` [`engines`] field -4. `>=8.0.0` +4. `>=16.0.0` -The default version is `8.0.0` because it's the minimum version the community is maintaining (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). +If you omit the [engines] field, this rule chooses `>=16.0.0` as the configured Node.js version since `16` is the active lts (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). For Node.js packages, using the [`engines`] field is recommended because it's the official way to indicate support: @@ -38,7 +38,7 @@ For Node.js packages, using the [`engines`] field is recommended because it's th "name": "your-module", "version": "1.0.0", "engines": { - "node": ">=8.0.0" + "node": ">=16.0.0" } } ``` @@ -50,7 +50,7 @@ For [Shareable Configs](https://eslint.org/docs/latest/developer-guide/shareable ```json { "n/no-unsupported-features/es-syntax": ["error", { - "version": ">=8.0.0", + "version": ">=16.0.0", "ignores": [] }] } @@ -144,7 +144,7 @@ For Example: { "settings": { "node": { - "version": ">=8.0.0", + "version": ">=16.0.0", } }, "rules": { diff --git a/docs/rules/no-unsupported-features/node-builtins.md b/docs/rules/no-unsupported-features/node-builtins.md index bbdeeab8..9e121d5e 100644 --- a/docs/rules/no-unsupported-features/node-builtins.md +++ b/docs/rules/no-unsupported-features/node-builtins.md @@ -21,9 +21,9 @@ This rule gets the supported Node.js version range from the following, falling b 1. Rule configuration `version` 2. ESLint [shared setting](http://eslint.org/docs/user-guide/configuring.html#adding-shared-settings) `node.version` 3. `package.json` [`engines`] field -4. `>=8.0.0` +4. `>=16.0.0` -The default version is `8.0.0` because it's the minimum version the community is maintaining (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). +If you omit the [engines] field, this rule chooses `>=16.0.0` as the configured Node.js version since `16` is the active lts (see also [Node.js Release Working Group](https://github.com/nodejs/Release#readme)). For Node.js packages, using the [`engines`] field is recommended because it's the official way to indicate support: @@ -32,7 +32,7 @@ For Node.js packages, using the [`engines`] field is recommended because it's th "name": "your-module", "version": "1.0.0", "engines": { - "node": ">=8.0.0" + "node": ">=16.0.0" } } ``` @@ -44,7 +44,7 @@ For [Shareable Configs](https://eslint.org/docs/latest/developer-guide/shareable ```json { "n/no-unsupported-features/node-builtins": ["error", { - "version": ">=8.0.0", + "version": ">=16.0.0", "ignores": [] }] } @@ -343,7 +343,7 @@ For Example: { "settings": { "node": { - "version": ">=8.0.0", + "version": ">=16.0.0", } }, "rules": {