From 633aae6903de1c9118d70538c63b0da26fca3ce2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=94=AF=E7=84=B6?= Date: Tue, 18 Apr 2023 11:50:03 +0800 Subject: [PATCH] docs: fix node lts statement --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 745eafa8..f3ce71b1 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ The rules get the supported Node.js version range from the following, falling ba 3. `package.json` [`engines`] field 4. `>=16.0.0` -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)). +If you omit the [engines] field, this rule chooses `>=16.0.0` as the configured Node.js version since `16` is the maintained 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: