From d04a96b84feb39a727695e067965b68568f8b8eb Mon Sep 17 00:00:00 2001 From: Tom Raine <157725735+WingRa7@users.noreply.github.com> Date: Sun, 31 Aug 2025 19:29:57 +0800 Subject: [PATCH] Update part9b.md: @types/eslint__js deprecated @eslint/js provides its own type definitions, so you don't need @types/eslint__js installed! --- src/content/9/en/part9b.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/9/en/part9b.md b/src/content/9/en/part9b.md index ad95b4e357..0ee388f866 100644 --- a/src/content/9/en/part9b.md +++ b/src/content/9/en/part9b.md @@ -898,7 +898,7 @@ What if we would like to restrict developers from using the *any* type? Fortunat Let's install ESlint and its TypeScript extensions: ```shell -npm install --save-dev eslint @eslint/js @types/eslint__js typescript typescript-eslint +npm install --save-dev eslint @eslint/js typescript typescript-eslint ``` We will configure ESlint to [disallow explicit any](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-explicit-any.mdx). Write the following rules to *eslint.config.mjs*: