diff --git a/package-lock.json b/package-lock.json index 40e12b2f7..3e48bd464 100644 --- a/package-lock.json +++ b/package-lock.json @@ -828,14 +828,13 @@ "dev": true }, "node_modules/@types/inquirer": { - "version": "8.1.3", - "resolved": "https://registry.npmjs.org/@types/inquirer/-/inquirer-8.1.3.tgz", - "integrity": "sha512-AayK4ZL5ssPzR1OtnOLGAwpT0Dda3Xi/h1G0l1oJDNrowp7T1423q4Zb8/emr7tzRlCy4ssEri0LWVexAqHyKQ==", + "version": "8.2.4", + "resolved": "https://registry.npmjs.org/@types/inquirer/-/inquirer-8.2.4.tgz", + "integrity": "sha512-Pxxx3i3AyK7vKAj3LRM/vF7ETcHKiLJ/u5CnNgbz/eYj/vB3xGAYtRxI5IKtq0hpe5iFHD22BKV3n6WHUu0k4Q==", "dev": true, "peer": true, "dependencies": { - "@types/through": "*", - "rxjs": "^7.2.0" + "@types/through": "*" } }, "node_modules/@types/json-schema": { @@ -14345,14 +14344,13 @@ "dev": true }, "@types/inquirer": { - "version": "8.1.3", - "resolved": "https://registry.npmjs.org/@types/inquirer/-/inquirer-8.1.3.tgz", - "integrity": "sha512-AayK4ZL5ssPzR1OtnOLGAwpT0Dda3Xi/h1G0l1oJDNrowp7T1423q4Zb8/emr7tzRlCy4ssEri0LWVexAqHyKQ==", + "version": "8.2.4", + "resolved": "https://registry.npmjs.org/@types/inquirer/-/inquirer-8.2.4.tgz", + "integrity": "sha512-Pxxx3i3AyK7vKAj3LRM/vF7ETcHKiLJ/u5CnNgbz/eYj/vB3xGAYtRxI5IKtq0hpe5iFHD22BKV3n6WHUu0k4Q==", "dev": true, "peer": true, "requires": { - "@types/through": "*", - "rxjs": "^7.2.0" + "@types/through": "*" } }, "@types/json-schema": { diff --git a/tsconfig.json b/tsconfig.json index a414b74e8..8d3243af4 100644 --- a/tsconfig.json +++ b/tsconfig.json @@ -26,5 +26,18 @@ // cannot leave it enabled. // See: https://github.com/microsoft/TypeScript/issues/49974 // "importsNotUsedAsValues": "error" + + // tsc has a clever and usually helpful feature ("@types support") + // wherein it automatically ingests any type definitions found in + // node_modues/@types/**/*.d.ts. This lets you tell it about the + // types for your favourite framework or library just by + // installing the relevant @types/ npm package. + // + // We don't (as of this writing) use this feature, and it causes a + // problem when one of our dependencies pulls in such a package + // which turns out to have syntax errors (see e.g. discussion on + // PR #6564: https://github.com/google/blockly/pull/6564), so + // disable it except for the explicitly-specified types. + "types": [], } }